The next generation of MCP

What this post added

The Model Context Protocol (MCP) has been updated to a stateless protocol, removing the need for stateful connections and Durable Objects for MCP servers. This simplifies deployment, scaling, and cost by allowing MCP servers to run on request-scoped infrastructure like Cloudflare Workers. Elicitation has been reworked with Multi Round-Trip Requests (MRTR) to remove the dependency on open streams. MCP requests now leverage HTTP headers (Mcp-Method, Mcp-Name) for method and name, enabling easier gateway and WAF integration. Authorization has been tightened with preferred client registration methods (pre-registered clients, Client ID Metadata Documents, Dynamic Client Registration) and RFC 9207 issuer identification. A formal feature lifecycle (Active, Deprecated, Removed) has been introduced for MCP features, with Roots, Sampling, Logging, Dynamic Client Registration, and the legacy HTTP+SSE transport being deprecated.