Rebuild your MCP servers stateless before July 28, or they break

If you run a production MCP server, you have a hard deadline. The 2026-07-28 spec removes the protocol-level session model entirely, and it's a breaking change.

The MCP release candidate makes every request carry its own protocol version, client info, and capabilities (Model Context Protocol Blog). A server that needed sticky sessions and a shared session store can now run behind a plain round-robin load balancer, routing on an Mcp-Method header. This is the largest MCP revision since launch. Servers built around session state will break.

I like this change, and I'll say why. Stateful protocols are where scaling pain lives. Sticky sessions mean you can't just add a box behind a load balancer. You need session affinity, a shared store, careful failover. Killing the session model at the protocol layer means MCP servers scale like any stateless HTTP service. That's the right architecture, and it's the kind of breaking change worth eating early.

The spec ships more than statelessness. The Tasks extension lets a server answer tools/call with a task handle the client drives via tasks/get, tasks/update, and tasks/cancel, which is purpose-built for index builds, deep searches, multi-minute jobs that today risk a client timeout (Stacktree). And Enterprise-Managed Authorization went stable, moving MCP access decisions to your IdP and killing per-server consent prompts (InfoQ).

This anchors a week saturated with MCP news. Apple shipped the Safari MCP server, the first official browser MCP from a major vendor. Microsoft's Agent Framework added Progressive MCP Disclosure so agents load and unload tool schemas on demand. And OX Security disclosed CVE-2026-30615, a zero-click chain where a cloned-repo README or poisoned tool description auto-registers a malicious MCP server into RCE, with 7,000+ publicly reachable MCP servers exposed.

What builders should do: make every request self-contained now. No session store, no server-side state between calls. Let clients cache tools/list. Wrap anything that might time out in a task handle. Then move auth to your IdP. You have until July 28. That's not much runway for a breaking protocol change.