FULL STORY

MCP's Major Update: Shifting to a Stateless Core

The Model Context Protocol (MCP) has released a release candidate for its largest update to date, fundamentally shifting the specification to a stateless core to enhance efficiency.

2026-07-22 ~ 2026-07-28 · 2 episodes · 11 posts

Episode 1 · MCP Protocol's Largest Update: Shifting to Stateless on July 28 (2026-07-22, 9 posts)

The Model Context Protocol (MCP) is set to finalize its largest specification update to date on July 28. The core change of this revision is a comprehensive shift from stateful to stateless, aimed at better supporting stateless load balancing and dynamic discovery. For developers, this eliminates the need for sticky sessions and favors horizontal scaling. This is not a standard patch but a substantial architectural migration.

Confirmed

To achieve statelessness, the new spec introduces several specific mechanisms:

- Completely removed the original `initialize` handshake process and `Mcp-Session-Id` via `SEP-2575`.

- Each request will inline carry its protocol version, client info, and capabilities via `_meta`, adding `Mcp-Method` and `Mcp-Name` headers.

- For scenarios where the server needs to initiate confirmations or other requests mid-call, a new MRTR (Multi Round-Trip Request) mechanism is introduced to replace the old state retention method.

Unconfirmed

According to developer @ialijr, this update deprecates the sampling feature, which some developers regretted. The community is currently actively discussing migration preparations and the specific impact.

Why it matters

The shift to statelessness brings significant scalability benefits but involves functional trade-offs. Developer @dfinke specifically clarified a key misconception: removing the protocol-layer session does not mean the application itself must become stateless. The changes primarily occur at the transport layer, and server applications can still maintain state using the MRTR mechanism.

Episode 2 · MCP Protocol Introduces Stateless Core in Major Update (2026-07-28, 2 posts)

MCP has released a release candidate for its 2026-07-28 specification, marking its largest revision to date. The update transitions the protocol to a stateless core, introduces an Extensions framework, and adds support for server-rendered UI.