← All IntelClip / Other
Old vs new MCP: stateful sessions vs single HTTP request
From Did Anthropic finally fix MCP? · ≈9:44
“The older stateful MCP which he refers to as legacy MCP required two HTTP requests.”
“And the new stateless version uses a single HTTP request, which is what it always should have been.”
“It's so much cleaner for both client and serverside implementations.”
What’s in it
- Explains why MCP dropped session IDs for a stateless design
- Shows how the new protocol cuts HTTP requests from two to one
- Details why stateless servers scale better for web apps
Clip transcript
came in it always stuck with the one server that was hit before. Now it doesn't matter. The older stateful MCP which he refers to as legacy MCP required two HTTP requests. One to initialize the session and obtain an ID and the second to actually start calling tools. But when the tool calls come in, it has to match this session ID and get routed to the right place, which means it has to be maintaining the connection. Obnoxious. And the new stateless version uses a single HTTP request, which is what it always should have been. It's so much cleaner for both client and serverside implementations. It's also a better fit for building scalable web apps since now you don't need to maintain serverside state to keep track of those session IDs or worry about routing the same session to the same
Recommended reads
Comments
Checking sign-in…
Loading comments…


