The mechanics are simple. The consequence is big. Until now, the server feeding tools to an AI agent remembered who it was talking to - a handshake at the start, a session number on every request after that. Which means it couldn't just be cloned behind a load balancer, because someone had to hold the state. The new specification removes exactly that.
Fact
The facts: the revision is dated 28 July 2026 and is published by the Model Context Protocol project, which lives under the Linux Foundation; the lead maintainers are David Soria Parra and Den Delimarsky. On 6 August, Cloudflare announced it supports the new specification across its agent stack, and that its endpoint accepts both the new and the old way of talking. The protocol drops the initial handshake and the session ID header; every request now carries the client's version and capabilities on its own. A mandatory call is introduced, through which the server declares what it supports. Headers naming the method and the tool become mandatory, so a gateway or firewall can route and count traffic without unpacking the content. Tool and resource lists now carry a cache lifetime and a scope - public or private. Roots, Sampling and Logging are marked deprecated, along with the old server-sent-events transport and dynamic client registration. For the first time there is a written policy: active, deprecated and removed states, with a minimum of 12 months between the last two.
Two things here we'll see play out fast. The first is cost - a server with no session memory can run on cheap infrastructure and scale by copies, with no shared storage underneath. The second is control: once the method name sits in the header, rate limiting, logging and caching happen at the edge, not somewhere deep in the application. That's exactly where security is cheap.
The spec belongs to the project, not to Cloudflare. Cloudflare is just the first to ship it in a product.
And one word about the name, because I've already seen it get muddled. Cloudflare's post URL contains "mcp-v2", but neither the specification nor the text talks about a second version. Protocol revisions are named by their date. It's a small thing, but exactly this kind of small thing is how arguments over who announced what get started.
The 12 months are the only firm planning signal in this whole story. Anything you've tied to dynamic client registration, to Roots, Sampling or Logging now carries an expiry date and belongs on the task list. It's not urgent today. But it has a date.
Official primary sources
MCP - the 2026-07-28 specificationMCP - changelogCloudflare - The next generation of MCPThe visual is generated code-art, no third-party images.