MCP Goes Stateless and Cuts Three Core Features in Biggest Spec Update
MCP's biggest spec update since launch goes stateless, deprecates Sampling, Roots, and Logging with a 12-month migration window
Takeaways
- MCP
2026-07-28finalizes today as the largest spec update since launch, making the protocol fully stateless at the transport layer. - Sampling, Roots, and Logging are formally deprecated under SEP-2577; all three remain fully functional for at least 12 months.
- The
Mcp-Session-Idheader and session handshake are removed with no grace period — this is the real hard break in the release. - Sampling's replacement is direct LLM provider API calls from the server; Roots' replacement is explicit tool parameters or resource URIs.
- A new formal lifecycle policy (Active / Deprecated / Removed) guarantees a minimum 12-month window before any deprecated feature can be removed.
- The release also ships MCP Apps, a Tasks extension, full JSON Schema 2020-12 for tools, and OAuth/OIDC authorization hardening.
The Model Context Protocol just shipped its largest specification update since launch. Version 2026-07-28 finalizes today, and it does something that will ripple through every MCP deployment: it makes the protocol stateless at the transport layer, and formally deprecates three features that have been part of MCP since the beginning: Sampling, Roots, and Logging.
MCP goes stateless
Previously, every client had to complete an initialize/initialized handshake and carry an Mcp-Session-Id header on every request, pinning it to a specific server instance. That session handshake is gone. Protocol version, client info, and capabilities now ride inline in a _meta field on every request, which means no sticky sessions, no shared Redis stores, and no deep packet inspection.
The practical payoff for anyone running MCP at scale is immediate: the stateless core scales on ordinary HTTP infrastructure. The release also ships server-rendered UIs through MCP Apps, long-running work through the Tasks extension, authorization aligned more closely with OAuth and OpenID Connect, and a formal deprecation policy so the protocol can evolve without breaking existing implementations.
What Sampling, Roots, and Logging actually do
Before getting into why they're being cut, here's what each feature does:
- Sampling (
sampling/createMessage): lets an MCP server ask the client to make an LLM completion on its behalf. The server sends a prompt, the client runs it through whatever model it has access to, and returns the result. - Roots (
roots/list): lets a client tell a server which directories or files it should operate on, providing workspace boundary hints. - Logging (
logging/setLevel,notifications/message): lets servers send structured log messages back to clients over the MCP wire.
Why cut them now?
The MCP specification aims to stay minimal. Each of these features has viable alternatives outside the protocol, and none are critical to the core resource/tool/prompt interaction model. The stateless redesign accelerated the decision: Sampling was architecturally tied to the old session model, because a server could only ask the client for a completion over a persistent, stateful connection. That assumption is now gone.