MCP Specification Transitions to 'Stateless' Design

The MCP (Model Context Protocol), a specification that standardizes communication between AI agents, underwent a major design overhaul in its July 28, 2026 update. Specifically, the 'initialization handshake,' an initial confirmation procedure performed at the start of connection, and session headers have been removed from the specification. In their place, headers indicating the request method name and tool name have been added as mandatory elements.

MCP is a protocol designed to standardize the interactions when AI agents invoke external tools or services. As 'gateways'—intermediary devices that connect multiple AI systems and services—become increasingly prevalent, the challenge of efficiently routing MCP-compliant traffic has emerged as a pressing issue. This update represents a response to that challenge.

The core of the change lies in making communication 'stateless.' Stateless refers to a design in which each request does not depend on the state of previous interactions, and the server does not need to maintain session information. The handshake and session headers that were removed are precisely the mechanisms responsible for maintaining that 'state.' Conversely, the newly mandatory method name and tool name headers allow gateways to determine destinations without parsing the JSON body.

Developers' reactions to this change are divided. Some developers point out that 'this is merely reinventing REST.' REST is an architectural style long used as a design principle for web services, and stateless communication is one of its fundamental principles. This raises questions about whether the change essentially renders MCP equivalent to an API.

Meanwhile, other developers argue that 'the meaning inherent in the specification itself remains unchanged.' According to their perspective, MCP's value lies not in any particular communication method, but in 'standardization' itself—enabling AI agents to invoke tools under a common set of rules. Even if the technical implementation has converged toward REST, the role MCP plays as a standard is not compromised.

This discussion can be viewed as demonstrating that 'communication standardization' is becoming an important practical concern as AI agents become more prevalent. As agent configurations that autonomously invoke multiple tools and services become common, routing efficiency at gateways directly impacts operational costs and response latency. The lightening of processing achieved through stateless design can be positioned as a practical advantage.

However, the question 'how does MCP differ from an API?' may continue to be raised within the community. It is natural for specifications to converge toward existing technologies as they mature, and the key focus for maintaining developer support may be the extent to which MCP can sustain its distinctive value.