The Model Context Protocol (MCP) released its largest revision since launch on July 28, 2026. The 2026-07-28 specification removes the initialize/initialized handshake and Mcp-Session-Id header, making MCP fully stateless at the protocol layer. Each request now carries its own protocol version, client identity, and capabilities, allowing any server instance to process any request without session affinity. All four Tier 1 SDKs (TypeScript, Python, Go, C#) shipped support on day zero.
This shift eliminates the need for sticky sessions, shared session stores, or Durable Objects to manage protocol state. MCP servers can now run on commodity serverless infrastructure—Cloudflare Workers, AWS Lambda, plain HTTP load balancers—without stateful coordination. Two new HTTP headers (Mcp-Method and Mcp-Name) let gateways and load balancers route and rate-limit requests by operation without inspecting the JSON-RPC body. Multi Round-Trip Requests replace server-initiated SSE streams: when a server needs input mid-call, it returns input_required with a payload; the client gathers the answer and retries the original call, allowing any instance to process the retry.
MCP also introduced Tasks as an official extension (moved from experimental), a formal extensions framework, header-based routing, cacheable list results (ttlMs + cacheScope modeled on HTTP Cache-Control), and OAuth 2.0 / OpenID Connect alignment. Roots, Sampling, and Logging features are deprecated with a 12-month removal window. AWS, Google Cloud, Microsoft, Anthropic, Figma, and Netlify all committed support. SDK was downloaded 97M+ times/month; 10,000+ MCP servers in production.
For architects: stateless MCP unbinds agent infrastructure from protocol sessions. Remote agents can now scale horizontally on standard web infrastructure—no sticky routing, no session stores, no protocol overhead for stateless use cases. The routing headers solve a long-standing API gateway pain point. Watch MCP server adoption in edge environments (Cloudflare Workers, Vercel Functions, Lambda@Edge) where session management was a dealbreaker; Tasks extension maturity and tool-schema upgrades (full JSON Schema 2020-12) expand what agents can express.