A coming update to the Model Context Protocol shifts to a stateless session model, removing a key obstacle for companies trying to run MCP servers at scale.
The Model Context Protocol (MCP) — the standard that lets AI models securely connect to external data sources and services — is receiving a significant update next week that makes it easier to run at large scale, according to TechCrunch [1].
For developers and companies building agentic AI products, the change matters because the current version of MCP has made it genuinely difficult to deploy servers that handle millions of users, and that friction has slowed real-world adoption [1].
What MCP does and why session IDs became a problem
MCP is, in practical terms, the plumbing that allows a chatbot to reach into a calendar, a database, or internal tools without engineers having to build a custom connection for every integration [1]. The protocol has been one of the core building blocks of AI interoperability, but its current session-handling design creates headaches at scale [1].
Under the existing system, when an MCP client — such as Anthropic’s Claude — first connects to a server, it sends an initial handshake that includes its version and capabilities, and the server responds with its own capabilities and a session ID [1]. That session ID travels with every subsequent request so the server can recognize the ongoing conversation [1].
The problem surfaces in real deployments. A server farm handling millions of users typically sits behind a load balancer that routes each incoming request to whichever machine is free, sometimes in a different region [1]. Under the current MCP design, every machine in that farm needs to know about session IDs that other machines originally issued — work that, as TechCrunch put it, “fights the load balancer instead of working with it” [1].
The fix: a stateless approach
The updated protocol takes a looser, stateless approach to session IDs on the server side, similar to how most ordinary websites already handle requests [1]. The official specification for the new version has been public since May, though an unusually detailed explanation of the changes came from the team at Arcade on Monday [1].
The stateless model should make MCP servers easier to maintain and, in theory, cheaper to run at scale [1]. TechCrunch noted that the scaling difficulty has been “part of the reason we haven’t seen more companies ship large-scale, first-party MCP integrations despite all the hype around agentic AI this year” [1].
The update is a reminder that AI infrastructure does not always move as fast as model development itself — standards-body consensus, as TechCrunch observed, moves on its own timeline [1].
Sources
This article was drafted with AI from the cited sources and checked against them before publication. Spot an error? Let us know.
