Next-Generation Version of MCP

MCP (Model Context Protocol) has changed to a fully stateless protocol with the 2026-07-28 specification. The TypeScript, Python, Go, and C# SDKs have also been updated to match the new specification, making it possible to operate MCP servers more simply and cheaply.

Existing MCP required maintaining session state based on the initialize·initialized handshake and the Mcp-Session-Id header. Because of this, auto-scaling infrastructure had to preserve active sessions, the deployment process required clearing or migrating sessions, and connections could break during instance failures.

In the new protocol, the mandatory handshake and protocol session have been removed from the core request path. Each request directly passes the protocol version, client identifier, and client capabilities, and server/discover is called selectively only when one wants to check server information in advance.

Accordingly, requests simply need to execute tools, prompts, and resources on the server and return the results. Since there is no need to store sessions, MCP servers can be operated on a single Worker, and the complexity of the deployment, scaling, and maintenance process is reduced.

Cloudflare has been building remote MCP servers by combining the Workers OAuth Provider and Durable Objects since releasing the McpAgent primitive in March 2025. Durable Objects remain valid when the application itself requires state storage, persistent storage, and real-time coordination, but in the new specification, it is no longer necessary to use McpAgent for MCP itself.