Cloudflare released the Model Context Protocol (MCP) v2 specification on 2026-07-28, rewriting the protocol to eliminate stateful sessions entirely. Previously, MCP servers required persistent Mcp-Session-Id headers, sticky session routing, open streams, and stateful infrastructure—typically Cloudflare Durable Objects—to maintain client-server continuity. The new specification removes the handshake, session headers, and protocol sessions from the core request path, allowing MCP servers to run on request-scoped infrastructure like Cloudflare Workers.
The shift eliminates major operational complexity: no more session migration, no autoscaling routing state, no risk of broken sessions on instance loss. Each request now carries its own protocol version, client identity, and capabilities. Multi-Round-Trip Requests (MRTR) replace stream-based elicitation, letting servers request additional input without holding a connection. The new TypeScript, Python, Go, and C# SDKs reflect these changes; Cloudflare's Agents SDK has supported the new spec since day one, with production traffic already validated before finalization.
For architects: this collapses the deployment barrier for agentic systems. MCP servers can now run as simple Workers functions with zero state management, dramatically reducing operational footprint. The removal of Durable Objects as a requirement, combined with HTTP semantics native to the protocol, opens MCP adoption to edge platforms, serverless containers, and resource-constrained environments—expect faster iteration cycles and lower infrastructure costs for teams building agent tooling pipelines.