What do the stateless core and header routing mean for gateways?
In short: The stateless core means each MCP request stands alone, with no handshake or session to track. Header routing means Streamable HTTP requests carry Mcp-Method and Mcp-Name headers. Together they let a gateway route, rate limit and apply policy per call without parsing bodies or pinning clients to one instance.
Why does statelessness matter?
Earlier versions needed a handshake and a session. Gateways had to keep sessions sticky or rebuild them.
Now any request can land on any instance, so gateways scale horizontally like ordinary HTTP proxies.
What can a gateway do with the new headers?
Mcp-Method names the operation, such as a tool call. Mcp-Name names the tool or resource.
A gateway can match policy, apply rate limits and write audit records from headers alone.
Does a gateway still need to read the body?
For routing and metering, no. For content checks such as secret masking or injection screening, the body still matters.
Sources
- MCP blog: 2026-07-28 release [mcp-0728] read 2026-11-03
Other explainers are listed on the spec hub.
By The Datasheet desk · Published and reviewed 2026-11-03