Your server has worked fine for a year. Then a client on the new spec connects and something's off: it never sends initialize, and your session-keyed state is empty. The July 2026 revision of MCP made the protocol stateless, and most tutorials on the web still describe the old handshake.
The good news: the official SDKs absorb most of it, and the old features keep working through a deprecation window of at least twelve months.
What changed
Before 2026-07-28
initialize/initializedhandshake opens a session.Mcp-Session-Idheader carries session state.- Servers send elicitation, sampling and roots requests over a held-open stream.
- Clients register for OAuth with Dynamic Client Registration.
From 2026-07-28
- No handshake: every request carries protocol version, client identity and capabilities in
_meta. Optionalserver/discoverfor capabilities up front. - No session ID. Streamable HTTP requests carry
Mcp-MethodandMcp-Nameheaders, so gateways can route them. - Multi round-trip requests: the server answers
resultType: "input_required", the client retries withinputResponses. - Client ID Metadata Documents (CIMD) replace DCR, which is deprecated.
Also new: cache hints (ttlMs, cacheScope) on list results, a deterministic order for lists, a single subscriptions/listen stream for change notifications, and a formal extensions framework (Tasks, MCP Apps and Enterprise-Managed Authorization are extensions).
Deprecated, with a window
- Roots, Sampling and Logging still work "for at least twelve months"; new implementations shouldn't adopt them. Log to stderr (stdio) or OpenTelemetry instead of protocol logging.
- The HTTP+SSE transport has a year-long off-ramp. Move to Streamable HTTP.
- Dynamic Client Registration is deprecated in favour of CIMD, with no removal date given yet.
Migrate, step by step
- Update the SDK. The blog lists TypeScript, Python, Go and C# as Tier 1 for 2026-07-28, with Rust in beta. In TypeScript, serve stdio with
serveStdio(createServer)so the same server answers new clients and clients that still open withinitialize; wiringserver.connect(new StdioServerTransport())by hand only serves older clients. - Remove session state. If you kept state per
Mcp-Session-Id, mint an explicit handle in a tool result (a cart ID, a job ID) and have the model pass it back as a tool argument. Bind it to the authenticated user and make it unguessable. - Replace server-initiated requests. Where you asked the user something mid-call (elicitation), return
input_requiredand let the client retry with the answer. - Check your gateway. If a proxy sits in front of your HTTP server, route on
Mcp-MethodandMcp-Nameinstead of session affinity. - Fix auth. Validate the issuer (
iss) before redeeming an authorization code, setapplication_typeif you support desktop or CLI clients with localhost redirects, and plan your move from DCR to CIMD. - Test both eras. List tools with the MCP Inspector in the
modernprotocol era and again in the defaultlegacyera.
npx @modelcontextprotocol/inspector --cli node build/index.js --protocol-era modern --method tools/list
npx @modelcontextprotocol/inspector --cli node build/index.js --method tools/listIn short
- No handshake, no session ID: every request describes itself.
- Old features keep working for at least twelve months; plan, don't panic.
- Explicit handles replace session state; MRTR replaces server-initiated requests.
What to try next
Share this lesson- Starting fresh instead? Build your first MCP server already targets 2026-07-28.
- Re-run the security checklist: handles and auth changed.