The July 2026 MCP spec update removes the protocol-level session layer, eliminating the need for sticky sessions and shared session stores for remote MCP servers. Operators have a 10-week migration window ending July 28, 2026 to update their infrastructure before the final spec ships. The shift enables horizontal scaling via round-robin load balancers but requires refactoring session-dependent code to use explicit client-passed handles.
The Model Context Protocol just deleted the session layer that 10,000+ public remote servers depend on, and you have until July 28 to migrate. The 2026-07-28 release candidate locked on May 21 removes the initialize handshake and Mcp-Session-Id header entirely, making every request self-contained. That sounds like a cleanup — until you realize your load balancer, your auth layer, and your long-running workflows all built assumptions around protocol-level sessions that no longer exist.
The Stateless Shift: What Actually Changed
The headline change is that MCP becomes stateless at the protocol layer. Six Specification Enhancement Proposals work together to get there, completing the plan the maintainers laid out in December.
If you enjoyed this, read the full post at SaaS with Alex
Top comments (0)