On July 28, 2026, the Model Context Protocol (MCP) will undergo its most significant architectural revision since its November 2024 launch. By transitioning to a fully stateless specification, the protocol removes the requirement for persistent connections and session-specific state, fundamentally altering how agent infrastructure is deployed and scaled.
Since its inception, MCP has relied on a stateful model that required an initial handshake and the maintenance of a Mcp-Session-Id header. This design created a significant bottleneck: load balancing was complex and resource-intensive because the protocol required sticky sessions.
The July 28 update eliminates the initialize handshake and the Mcp-Session-Id header entirely. In the new stateless architecture, any request can be routed to any server instance. This allows infrastructure teams to replace specialized, state-aware routing with ordinary load balancers.
The new specification introduces two mandatory headers: Mcp-Method and Mcp-Name (SEP-2243). These headers provide sufficient metadata for gateways and rate-limiters to make routing decisions at the edge. Multi Round-Trip Requests (MRTR) via SEP-2322 allows servers to return an InputRequiredResult instead of holding an SSE stream open.
As of May 2026, the official MCP servers repository has garnered 86,148 GitHub stars. The protocol has moved beyond early experimentation into a foundational layer for agentic systems, with broad industry backing from Anthropic, OpenAI, Microsoft, Amazon, and Google.