MCP Goes Stateless, and Developers Ask Whether That Just Makes It an API Again

August 12, 2026 | Source: InfoQ AI/ML

Tags: MCP, Model Context Protocol, agentic AI, Cloudflare, API management, stateless

MCP's July 2026 spec overhaul drops stateful sessions entirely and adds two mandatory HTTP headers (Mcp-Method, Mcp-Name) so gateways can route, throttle, and meter agent traffic by tool name without parsing JSON — aligning agent infrastructure with standard API management tooling.

Details

The Model Context Protocol's July 28, 2026 specification removes protocol sessions as a core concept. Previously, agents opened with an initialize/initialized handshake and maintained an Mcp-Session-Id header that pinned clients to specific server instances — making horizontal scaling difficult and load balancing impractical. Under the new spec, every request is stateless and carries everything it needs. True autoscaling becomes possible: any request can land on any instance, and deployments no longer need to drain or migrate session state. Infrastructure teams that previously had to special-case MCP traffic for session affinity can now treat it like any stateless HTTP API. The equally important change receiving less coverage: two new mandatory HTTP headers on Streamable HTTP requests. Mcp-Method signals the request type (e.g., tools/call) and Mcp-Name identifies which tool. This moves metadata out of the JSON-RPC payload and into the transport layer, where existing gateways, WAFs, and rate limiters already operate. Cloudflare's documentation shows this enables per-tool rate limiting and routing without body inspection. Tool arguments can also be copied into headers for custom routing logic. Server-initiated elicitation changes too: holding an open stream is replaced by a two-round-trip Multi Round-Trip Request pattern. Simpler to deploy, but adds latency for human-in-the-loop approval workflows. Developer discussion is actively debating whether these changes blur the line between MCP and standard REST APIs.