MCP Protocol's Largest Update Finalizes on July 28: Shifts to Stateless
The MCP (Model Context Protocol) is set to finalize its largest specification update to date on July 28. According to developer @dfinke, the core change of this revision is a complete transition from stateful to stateless, aiming to better support stateless load balancing and dynamic discovery.
Key Details and Architectural Changes
To achieve statelessness, the new specification introduces several specific mechanisms: First, `SEP-2575` completely removes the original `initialize` handshake process and Session ID. Second, each request will inline its protocol version, client information, and capability description via `_meta`, while adding `Mcp-Method` and `Mcp-Name` request headers. Additionally, for scenarios where a server needs to initiate confirmations or other requests midway through a call, the new spec adopts a brand-new MRTR (Multi-Request Transaction Routing) mechanism to replace the previous state-maintenance approach.
2026-07-22 ~ 2026-07-23 · 8 related posts
- July 28 MCP update makes stateful servers stateless — dfinke · 2026-07-22
- Largest MCP Revision Goes Stateless, Drops Initialize Handshake and Session IDs — dfinke · 2026-07-22
- MCP Architecture Update: Enables Stateless Load Balancing and Dynamic Discovery — dfinke · 2026-07-22
- Largest MCP spec update moves servers from stateful to stateless — dfinke · 2026-07-22
- [source] Protocol sessions go away, but apps can stay stateful with MRTR — dfinke · 2026-07-22
- [source] MCP v2 Finalizes Next Week: Stateless, Sampling Deprecated, Developers Discuss Migration — ialijr · 2026-07-22
- MCP 2026-07-28 removes sessions and turns the protocol stateless — Substantial-Heat-321 · 2026-07-23
1 near-duplicate retellings: dfinke