Google engineering post details the stateless rework behind the 2026-07-28 revision

Google published an engineering post on 2026-08-05 describing its role in the stateless redesign that shipped in the MCP 2026-07-28 revision. The authors, Kurtis Van Gent of Google Cloud Data and Alan Blount of Google Cloud AI, write that "Google led the charge to decouple the protocol from stateful transport constraints" and that the company co-founded the MCP Transports Working Group together with Hugging Face and other industry partners.

The post explains the revision's infrastructure consequences from the operator's side. Because every request is now self-describing, MCP servers no longer need session state pinned to a specific instance, which the authors say enables standard load balancing and running "MCP servers as serverless functions on platforms like Google Cloud Run or Google Cloud Functions." It also walks through the header-routing model: streamable HTTP requests carry Mcp-Protocol-Version, Mcp-Method, and Mcp-Name headers, so proxies and gateways can route traffic without parsing JSON-RPC bodies.

As production evidence the post points to GitHub: "Major production servers, such as the GitHub MCP Server, have already upgraded to this spec and completely removed Redis session storage, eliminating database writes and reads on every single call."