The next generation of MCP

Summary

Model Context Protocol previously required stateful connections between clients and remote servers, creating operational complexity around sticky sessions, message replay, and open streams. The newly released MCP 2026-07-28 specification transitions MCP to a fully stateless protocol alongside updated SDKs across TypeScript, Python, Go, and C#. The protocol eliminates mandatory handshakes and session identifiers from core request paths while enabling servers to run on request-scoped infrastructure like Cloudflare Workers. Interactive elicitation is restructured through Multi Round-Trip Requests, which allow servers to return input requirements without sustaining persistent connections. Standardized headers for method names and improved OAuth authorization mechanisms further enable standard web infrastructure to inspect and manage MCP traffic efficiently.

Takeaways

1. 1

   The MCP 2026-07-28 specification removes required handshake sessions and Mcp-Session-Id headers, allowing MCP servers to run statelessly on standard serverless infrastructure.

2. 2

   Multi Round-Trip Requests replace open streams for elicitations by allowing servers to return an input_required status that clients answer in a follow-up retry.

3. 3

   Streamable HTTP requests now include Mcp-Method and Mcp-Name headers, enabling gateways, rate limiters, and firewalls to route and inspect traffic without parsing JSON bodies.