INFRA Signal 579
The next generation of MCP
↗
MCP has been re-engineered as a stateless protocol, letting servers run on Cloudflare Workers without Durable Objects or session management.
Removing the required session handshake eliminates the need for sticky routing, open streams, and coordination layers, which simplifies scaling and reduces infrastructure cost. Engineers can now host MCP endpoints on request-scoped serverless platforms, cutting operational overhead while retaining full protocol functionality. Existing applications that need persistent data must still provide their own storage, but the protocol itself no longer imposes stateful requirements.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The protocol no longer uses a handshake or session identifier, making each request self-contained.
MCP servers can be deployed as plain Workers, removing the dependency on Durable Objects or other stateful primitives.
Updated SDKs introduce a createMcpHandler migration path, and early adopters are already running the new version in production.
THE READ
What the cluster adds up to.
The core change is the shift from a stateful connection model to a fully stateless request model. Previously, a server had to allocate a session ID and keep that state across multiple calls, which forced infrastructure to preserve session affinity and manage long-lived streams. The new specification drops the handshake and session header, embedding version, identity, and capability data directly in each request. This redesign removes a large source of complexity for MCP deployments.
Because the protocol no longer requires per-session state, MCP endpoints can be hosted on Cloudflare Workers, a request-scoped serverless environment. Workers do not maintain persistent connections, so they fit the stateless model naturally and can scale instantly without coordination. The removal of Durable Objects for MCP alone reduces the number of moving parts and lowers operational cost, though Durable Objects remain useful for applications that need their own persistent storage.
Developers will need to adopt the refreshed SDKs for TypeScript, Python, Go, and C#, which expose a new createMcpHandler entry point in place of the older McpAgent primitive. Migration involves updating code to the new handler and removing any reliance on session IDs or sticky routing logic. Early customers have already moved to production with the release candidate, indicating that the migration path is functional and does not require major architectural changes beyond the SDK update.
The stateless design does not eliminate the need for state when an application itself requires it. Any workflow that depends on persisted data must still integrate external storage or continue using Durable Objects for that purpose. Consequently, engineers must separate protocol handling (now stateless) from application state management, ensuring that any needed persistence is provided by a separate layer.
For teams building or operating MCP services, the practical impact is a simpler deployment pipeline, faster autoscaling, and fewer failure modes related to session loss. The trade-off is the responsibility to handle any required state outside the protocol, which may involve adding databases or other storage services. Overall, the change streamlines infrastructure while preserving the full feature set of MCP.
Written by elseif from the cluster below · checked for specifics the sources never containedTHE CLUSTER