signal insight

Cloudflare rewrites MCP as a fully stateless protocol that runs in a single Worker

On August 6, 2026 Cloudflare detailed the next generation of the Model Context Protocol: the 2026-07-28 spec, interaction model, and SDKs were rewritten to be fully stateless, so MCP servers can run in a single Cloudflare Worker with no stateful session infrastructure.

Published Aug 6, 2026 Updated Aug 8, 2026 1 sources

CloudflareModel Context Protocolagentsopen source releasehigh impact

agentsenterprise-controlsinfrastructureai-coding-toolsopen-source release

Impact: high
Confidence: 80%
Change type: open source release
First seen: Aug 6, 2026
Last updated: Aug 8, 2026
Audience: developersplatform teams
Status: Ready

Summary

What changed

August 6, 2026: MCP became a fully stateless protocol. The 2026-07-28 specification shipped with rewritten TypeScript, Python, Go, and C# SDKs, dropping the initialize and session-id model so MCP servers can run in a single Worker with no stateful infrastructure.

Why it matters

Removing session state lets MCP servers autoscale like ordinary serverless functions instead of pinning connections to instances, lowering cost and operational complexity and making Workers a natural default host for the fast-growing MCP server ecosystem.

Evidence excerpt

MCP servers can now run in just a Worker, with no stateful infrastructure needed.

Sources

blog.cloudflare.com