Revolution in MCP Protocol: Transition to Stateless Architecture
With MCP 2026-07-28 specification, servers no longer require stateful connections.
1Evolution of MCP
The Model Context Protocol (MCP) has become the universal standard for agent interactions with external services over the past year and a half. However, MCP's stateful connections were criticized. This stemmed from MCP's initial STDIO transport protocol designed for local applications. When servers went remote, this statefulness was carried over to web infrastructure, creating complexity.
2New Specification
The MCP 2026-07-28 specification was released last week, alongside updates to TypeScript, Python, Go, and C# SDKs. MCP is now a fully stateless protocol, allowing servers to run within a Worker, offering operational simplicity and cost benefits.
3Cloudflare's Role
Cloudflare began its journey with MCP in March 2025 with the McpAgent primitive. Two months later, an MCP Demo Day featured companies like Asana, Atlassian, and Block. Cloudflare launched MCP Server Portals to facilitate enterprise adoption.
4Durable Objects
Cloudflare Durable Objects were uniquely positioned for MCP, combining compute, persistent storage, and real-time coordination. However, it became clear that MCP needed to be simpler and more efficient.
5Stateless MCP
Previous MCP transports required an initialize and initialized exchange to start a session. The new protocol removes this handshake and the Mcp-Session-Id header. Each request carries protocol version, client identity, and capabilities.
6Elicitation Change
MCP servers sometimes needed more information to complete a request. Server-initiated requests like elicitation/create depended on an open stream. The new protocol simplifies this with Multi Round-Trip Requests (MRTR).
7HTTP Infrastructure
MCP requests are JSON-RPC messages sent over HTTP. Previously, request information was only in the JSON body. The new protocol moves this information to HTTP headers, making infrastructure more understandable.
8Customer Feedback
Cloudflare tested the new specification's release candidate with customers and partners. This provided confidence that the migration path from McpAgent to createMcpHandler works with production traffic.
9Operational Advantages
The new MCP specification allows servers to scale faster. MCP servers can now run on request-scoped infrastructure like Cloudflare Workers, without needing Durable Objects.
10Ease for Developers
The new protocol simplifies the deployment, scaling, and maintenance of MCP servers. This enables more developers to build rich agent applications.
11Future Perspective
MCP's transition to a stateless architecture could increase its future adoption. This change may allow MCP to find broader applications.
12Conclusion
The MCP 2026-07-28 specification reduces protocol complexity while preserving all functionality. This makes MCP servers more efficient and scalable.
Original article: Cloudflare Blog — MCP Protokolünde Devrim: Stateless Yapıya Geçiş