Latest MCP spec removes session affinity for remote servers
Interrupted operations may need retries, so side-effecting tools need to handle repeat calls safely.
The latest MCP specification removes protocol-managed sessions, letting remote server requests go to any available instance and reducing the need for infrastructure dedicated to session handling. It also eliminates the initialization exchange and the Mcp-Session-Id header. Because stream resumption is no longer supported, clients may have to retry interrupted operations, making idempotency important for tools that cause side effects. Apify is adding stateless support alongside its sessionful server, while AWS recommends that gateways track protocol versions and keep legacy session infrastructure until older-client traffic has ended.
Why it matters
For operators, server capacity becomes less dependent on keeping a client on a particular instance, and infrastructure used only for sessions can be removed. For clients, a dropped stream may mean retrying an operation; tools with side effects need to avoid repeating those effects. Older-client traffic still needs to be accounted for before session infrastructure can be retired.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.