The next generation of MCP

The July 28, 2026 revision of Model Context Protocol changes how an AI client maintains contact with a tool server. As Cloudflare explains in its implementation account, requests carry the information needed to handle them independently, removing the protocol's required session setup and stored session identity.

That also changes requests for human input. A server can return a request for more information, then receive a new call containing the answer, instead of keeping a connection open while it waits. Servers can consequently process these interactions as ordinary web requests. Applications still need storage for their own persistent data, but the communication protocol no longer imposes that requirement by itself.

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

“Building a well-behaved MCP Server meant managing request routing to sticky sessions, holding open streams, message replay, and generally more overhead and complexity than a traditional web server.”

“MCP is now a fully stateless protocol.”

“This means that MCP servers can now run in just a Worker, no stateful infrastructure needed”