OFICIAL Cloudflare Blog Gadgets · Aug 06, 2026

The next generation of MCP

What happened

Based on Cloudflare Blog · Aug 06, 2026

Cloudflare and the Model Context Protocol (MCP) team released MCP 2026-07-28, a stateless protocol update that removes session management requirements, simplifying server deployment and reducing operational overhead for developers.

🚩 Report a correction ↗ Open source

Cloudflare Blog — Cloudflare

Key points

Over the last year and a half, the Model Context Protocol (MCP) has become the universal standard for how agents interact with external services.

But one of the main criticisms of MCP was that the protocol required a stateful connection between Client and Server.

This evolved from MCP’s origins and the first STDIO transport, designed for local applications.

When MCP Servers went remote, it translated the stateful connection that worked so well locally and transposed it onto web infrastructure.

Key numbers

The Model Context Protocol (MCP) has been updated to version 2026-07-28, transitioning from a stateful to a stateless protocol. This change eliminates the need for session management, sticky routing, and persistent connections, which previously required complex infrastructure such as Durable Objects. The update applies to the specification, interaction model, and SDKs in TypeScript, Python, Go, and C#. Developers can now deploy MCP servers using stateless platforms like Cloudflare Workers, reducing operational complexity and costs.

Cloudflare introduced MCP support in March 2025 with its McpAgent primitive, followed by an MCP Demo Day in May 2025 featuring customers including Asana, Atlassian, Block, Intercom, Linear, PayPal, Sentry, Stripe, and Webflow. The company later released MCP Server Portals to help enterprises adopt MCP securely. While Durable Objects were initially suitable for stateful MCP servers, the new stateless protocol removes this dependency, enabling faster scaling and simpler deployments on request-scoped infrastructure.

The protocol now removes the mandatory handshake, session headers, and protocol sessions from the core request path. Each request includes the protocol version, client identity, and required capabilities, with optional discovery via server/discover. This change eliminates the need to preserve active sessions, reducing deployment complexity and improving scalability. MCP servers can now process requests without maintaining state, making them easier to deploy, scale, and maintain over time.

Additional updates include Multi Round-Trip Requests (MRTR) for server-initiated interactions like elicitations, standardized headers for HTTP requests, and tightened authorization requirements. The specification also introduces a formal feature lifecycle and deprecates Dynamic Client Registration (DCR) by summer 2027. Cloudflare’s Workers OAuth Provider now supports these requirements, allowing MCP servers on Workers to implement the new protocol seamlessly.

Original source → Deals on Clipraptor.com →