MCP Deleted Sessions — and 400M Monthly SDK Downloads Have to Follow
The 2026-07-28 spec removed the initialize handshake, the session ID, and stream resumability. Every MCP server you run against a stateful assumption is now on a migration clock.
NeuroX AI · July 30, 2026
The 2026-07-28 MCP specification shipped Tuesday with nine major changes, and the headline one is a deletion: the initialize/initialized handshake and the Mcp-Session-Id header are gone. MCP is now request/response. Anthropic put the blast radius in writing — 400M monthly SDK downloads, 4x growth over the year, and 950+ servers in Claude's connectors directory.
Statelessness is the win. Any request can hit any instance, so servers run behind a plain round-robin load balancer with no sticky sessions, on serverless and edge. Servers that need cross-call state now mint explicit handles and pass them as ordinary tool arguments — state becomes your data model instead of the transport's.
The cost is in what else went away. SSE resumability and message redelivery are removed: a broken response stream loses the in-flight request, and the client must re-issue it with a new request ID. Roots, Sampling, and Logging are deprecated under a new twelve-month window. Server-initiated requests are replaced by Multi Round-Trip Requests, where the server returns input_required and the client retries with answers attached.
None of that breaks a demo. All of it breaks a production integration you wrote against the old shape and haven't touched in six months. Protocol revisions are exactly the work that separates a prototype from a system.