MCP Goes Stateless, and Developers Ask Whether That Just Makes It an API Again
MCP's biggest update in 18 months strips away session state. Developers are split: progress or step backward?
Why it matters
A major protocol revision for agent-to-agent and agent-to-tool communication removes complexity but reignites debate over whether standardization solves real problems or just reinvents the wheel.
The key facts
8 to knowMCP 2026-07-28 spec removes initialize handshake and session headers
New required method and tool-name headers enable stateless gateway routing without JSON parsing
Developer reaction divided: some see REST rediscovery, others defend protocol-first approach
Affects agent infrastructure and routing at scale
MCP 2026-07-28 removes initialize handshake and session headers
Spec adds required method and tool-name headers for gateway routing without JSON parsing
Developer split: some call it REST rediscovery, others defend protocol standardization as the win
Change enables stateless gateway routing for agent traffic
Go to the source
InfoQ AI/MLinfoq.com
Publisher excerpt: The MCP 2026-07-28 specification removes the initialize handshake and session header, and adds required method and tool-name headers so gateways can route agent traffic without parsing JSON. Reaction split between developers calling it a rediscovery of REST and those arguing the standard itself was…