MCP Goes Stateless. The Release Candidate Drops Session Headers, Adds Extensions. Every MCP Server Developer Has Until July 28.

The protocol that powers 14,000+ servers just made a breaking architectural change. If you run an MCP server, your migration clock started four days ago.

The Model Context Protocol specification release candidate, locked May 21, removes the initialize/initialized handshake and the Mcp-Session-Id header entirely. The protocol is now stateless at the transport layer. Any request can land on any server instance without sticky routing. For anyone running MCP servers behind a load balancer with session affinity, this changes how you deploy.

The RC also introduces an Extensions framework with two official extensions: MCP Apps (servers that render HTML interfaces) and Tasks (long-running work that persists across requests). Six authorization hardening changes align MCP with OAuth 2.0 and OpenID Connect. There's a formal deprecation policy now, with 12-month minimum windows for breaking changes going forward.

Timeline: final specification publishes July 28, 2026. Tier 1 SDKs expected to ship support within a 10-week validation window.

I think going stateless is the right call. Stateful protocols are painful at scale. Sticky sessions create single points of failure. Session migration during deployments is a nightmare. But "right call" doesn't mean "easy migration." Every MCP server that relied on the session handshake or stored conversation state in server memory needs to externalize that state to a database or cache.

The Extensions framework is worth paying attention to separately. MCP Apps means servers can now render interactive UIs, not just serve data. Tasks means agents can kick off long-running work and come back for results later. These open up use cases that the original prompt-response MCP couldn't handle.

Context7, the most popular MCP server at 54,000 stars and 890,000 weekly npm downloads, will presumably adapt quickly. But the long tail of 14,000+ community servers is where the pain will be. If you're building on MCP, start reading the RC spec now. Don't wait for the final publication.