Cloudflare details stateless model Context protocol release
Drafted by our automated systems from the sources listed at the end of this article, and reviewed before publication. Every fact here should be traceable to one of those links; we publish no benchmark, price or figure that a linked source does not state. Where a company makes a claim about its own product, we report it as their claim.
Cloudflare published details regarding the latest Model Context Protocol specification, released last week. The update transitions MCP into a fully stateless protocol. Earlier versions relied on stateful connections originating from local application transports. When remote servers adopted this model, developers had to manage sticky sessions, open streams, and message replay. According to Cloudflare, the new specification removes the required handshake, the Mcp-Session-Id header, and protocol sessions from the core request path. Each request now carries its own client identity, client capabilities, and protocol version.
SDK updates and deployment changes
Updated TypeScript, Python, Go, and C# SDKs launched alongside the specification. Cloudflare states that the removal of protocol sessions eliminates the need for McpAgent, which was released in March 2025 using the Cloudflare Agents SDK. Servers can now run on request-scoped infrastructure such as Cloudflare Workers without requiring sticky sessions or persistent connection handling. And, server-initiated elicitations no longer depend on open streams. The protocol now uses Multi Round-Trip Requests, where a server returns an input required result and the client retries the operation after gathering the necessary user response.
Sources
- The next generation of MCP — Cloudflare, 6 August 2026