MCP’s biggest update removes the machinery many servers were built around - The New Stack

What the report says

Thenewstack.io reported that the Model Context Protocol (MCP) is undergoing its largest revision, with a release-candidate rewrite that removes two core pieces many implementations had depended on: sessions and the initialization handshake. The change replaces that machinery by moving protocol state into handles, according to the publisher’s snippet.

The practical effect, as described by The New Stack, is that remote MCP servers will behave more like stateless HTTP services. That is a significant architectural shift for developers and vendors who built servers around persistent session tracking or a negotiated start-up exchange. Existing projects may need to revisit assumptions about connection lifecycle, state storage and compatibility with clients using the newer protocol.

MCP is commonly used as a way for AI applications and agents to connect with external tools, data sources and services. In general web infrastructure, stateless HTTP-style designs can simplify scaling, routing and recovery because requests carry or reference the state they need instead of relying on a long-lived server-side session. However, the supplied article text does not provide migration timelines, compatibility guarantees or named maintainers behind the decision.

The development matters because MCP has quickly become part of the tooling conversation around AI agents and developer platforms. A change at this level affects not just protocol specification authors, but also framework maintainers, server operators and teams building integrations that expect MCP endpoints to behave consistently across local and remote environments.