Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

MCP's July spec killed sessions — tooling may not know

Written November 9, 2026

The July 28 MCP spec removed sessions and Mcp-Session-Id. Tooling that correlates sessions breaks silently. What changed, and the check.

The problem it solves

A builder whose MCP tooling correlates sessions by Mcp-Session-Id is running against a spec that removed sessions on July 28, 2026 — and the breakage is silent, not an error. The change itself is months old; what is new is an October 29 analysis by the Cloud Security Alliance that names the risk plainly: tooling that correlates activity via session IDs, or makes policy decisions during the initialization handshake, can lose visibility without reporting an error.

What changed on July 28

The 2026-07-28 specification turns MCP from a bidirectional stateful protocol into a request/response stateless one. The initialize/initialized handshake is retired along with the Mcp-Session-Id header. Every request now travels on its own, carrying its protocol version, client identity, and client capabilities in _meta — so any request can land on any server instance behind a plain round-robin load balancer, with no shared storage and no session affinity.

State did not disappear; it moved. If a server needs to carry state across calls, it mints an explicit handle from a tool and the model passes it back as an argument — a string the model can see, store, expire, and revoke, instead of session state hidden in the transport.

The same revision replaces server-initiated requests with Multi Round-Trip Requests (MRTR): a server that needs input mid-call answers with resultType: "input_required" and the client retries with the answers attached. Streamable HTTP requests must now include Mcp-Method and Mcp-Name headers, so gateways can route and authorize on headers instead of parsing bodies. Roots, Sampling, and Logging are deprecated — still working, with at least a twelve-month window before removal — and the legacy HTTP+SSE transport is deprecated too. The TypeScript, Python, Go, and C# SDKs were updated to match; the Rust SDK supports the new spec in beta.

The check

Search your MCP clients, servers, and gateways for session handling built on the old spec:

For each hit, the fix is the spec's own replacement: mint an explicit handle from a tool for cross-call state, and rebuild monitoring from session IDs to the Mcp-Method and Mcp-Name headers plus OpenTelemetry trace propagation.

Verdict

Treat any MCP tooling that stores sessions as suspect until you have grepped it. The spec removed the session in July, the SDKs have moved on, and the failure mode is not an error message — it is monitoring and policy quietly going blind. The check above takes an afternoon; the alternative is finding out from an incident.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: MCPhantom: agents install dead MCP servers · 140 silent MCP contract changes, and how to pin them · Pick a memory server for your coding agent · Agent Skills joins the Agentic AI Foundation