Is MCP 2026-07-28 backward compatible with session-based clients?

Do not assume wire-level compatibility. The revision removes initialize, initialized, protocol sessions, and Mcp-Session-Id, so mixed clients and servers need explicit version detection and tested adapters or parallel paths.

Does stateless MCP eliminate all state?

No. It removes protocol transport sessions. Servers can preserve cross-call state through explicit handles passed in tool arguments and durable application storage.

Why does stateless MCP help load balancing?

Independent self-describing requests can be handled by any compatible instance instead of relying on session affinity to an in-memory protocol session.

AI Agent - Aug 6, 2026

MCP Stateless vs Session-Based Compatibility

Quick answer

Stateless MCP and session-based MCP are materially different wire contracts. The 2026-07-28 revision removes initialization and Mcp-Session-Id, places version and capabilities on every request, and adds server/discover. Do not point an untested older client at a new-only server and assume negotiation will repair the mismatch.

Compatibility comparison

Concern	Session-based protocol	Stateless 2026-07-28 protocol
Connection setup	Initialization handshake	Independent requests
Routing	May require session affinity	Any compatible instance can handle a request
State	Often coupled to session	Explicit handle and application storage
Failure recovery	Session loss can interrupt work	Retry can reach a healthy instance, subject to idempotency
Capability exchange	Startup negotiation	Per-request metadata and optional preflight discovery
List behavior	May vary by connection	List endpoints no longer vary per connection

Stateless routing improves infrastructure flexibility, but a retried mutation can still duplicate work unless the application enforces idempotency.

Mixed-version rollout

Record every client and server protocol version.
Use server/discover where supported and preserve a documented older probe path only where required.
Route old and new traffic to explicit compatibility surfaces.
Test list results, tool calls, resources, prompts, notifications, errors, auth, retries, and long-running tasks.
Compare semantic results, not only successful HTTP status.
Remove the older path only after observed traffic and rollback criteria are satisfied.

Use the migration guide for the implementation sequence and the HTTP governance guide for gateways.

Frequently asked questions

Is it automatically backward compatible?

No. Removed handshake and session fields require explicit detection and tested compatibility behavior.

Is all state gone?

No. Only protocol-level session state is removed. Application state remains explicit.

Why is load balancing easier?

Self-describing independent requests do not require an in-memory protocol session on one pinned instance.

Official sources

Source check: August 6, 2026. Verify final spec and SDK compatibility before changing production routing.