← Back to feed

Anthropic published the MCP 2026-07-28 specification on July 28, the largest update to the Model Context Protocol since its launch. The change is architectural: MCP’s official core has moved from stateful sessions — where a server had to track a persistent client connection across requests — to stateless, independent request-response interactions. Any server instance can handle any request. No session memory required.

What Changed

The original MCP design expected servers to maintain an ongoing connection with each client. That made production deployments complex. Scaling required sticky routing — directing each client to the same server instance throughout a session. Restarting a server instance mid-session could break client state. Serverless and edge environments, which destroy and recreate instances on demand, were effectively incompatible with the protocol as designed.

The 2026-07-28 spec eliminates that constraint. Protocol version, client identity, and capability information now travel in the _meta parameter with each individual request, rather than being established at session initialization and assumed to persist. The result is a protocol that behaves like the Claude Messages API: stateless by design, horizontally scalable, compatible with any cloud deployment model.

Anthropic describes the change as moving MCP “closer to standard HTTP conventions.” The practical implication is that MCP servers can now be deployed as standard cloud functions — no special infrastructure, no session affinity requirements, no shared state to maintain across restarts.

What Moved to Extensions

The spec simultaneously separates richer protocol features into optional extensions rather than mandatory core behavior. Interactive interfaces (Elicitation, sampling) and long-running background tasks are now extensions that deployments can opt into rather than capabilities every MCP server must support.

This split matters for the enterprise adoption curve. Operators who need simple tool execution can deploy a minimal stateless server. Operators running long-horizon agent workflows can adopt the extensions that support those use cases. The core is smaller and more predictable; the optional layers accommodate complexity.

Deployment Implications

The stateless change directly addresses three production pain points that had accumulated since MCP’s initial release:

Load balancing. Standard load balancers can now distribute MCP requests across any available server instance. Sticky sessions, which add complexity and reduce resilience, are no longer required.

Cold starts. Serverless deployments that spin up new instances per request now work without session state loss. This opens MCP to Lambda, Cloud Run, and edge compute deployments that were previously impractical.

Restarts and rolling deployments. Server upgrades no longer require draining connections. Any instance at any version can handle any stateless request from any client.

The auth model was also hardened in the same update, though Anthropic has not published the specific changes separately.

Rollout

Support is shipping across Claude products but has not landed everywhere simultaneously. The spec is live; client and server implementations require updates to conform to the new stateless model. Anthropic’s existing Claude tooling is being updated in sequence.

For developers running MCP servers in production, the update requires reviewing session initialization logic and removing any state that was previously stored server-side across request boundaries. The transition is not backward-compatible at the implementation level, though Anthropic has indicated transition guidance is forthcoming.

The stateless shift makes MCP a fundamentally different deployment target than it was at launch — one that fits ordinary cloud infrastructure rather than requiring purpose-built session management.