MCP goes stateless, making serverless deployments and scale-to-zero much easier
Arindam_1729 · x · 2026-07-29
A post argues that the latest MCP spec makes deployment much easier by making the protocol stateless.
Key changes:
- The initialize handshake is removed.
- Servers are expected to treat every request independently, with protocol version and capabilities carried in meta.
- Sticky sessions are no longer required, so any replica can handle any request.
- Rolling deploys, scale-to-zero, and serverless hosting become much simpler.
- tools/list and server/discover can be cached with TTLs to reduce startup latency.
- Long-running work moves to the Tasks API instead of open connections.
The tradeoff is more bytes per request, since each call now carries metadata and client identity. The post also notes that sampling is being deprecated, with server authors expected to bring their own API keys and choose their own models.
Related event: Anthropic Launches Major MCP Update with Stateless Architecture(25 posts)→
More from coding & agent
- Eragon adds routing across 350+ models via Merge API for agent orchestration — shensi · 2026-07-30
- Agent Retrieval Bench shows coding agents often fail before patch generation even starts — Bowen Qin · 2026-07-30
- When MCP servers drift, user settings may stop applying to the capability you meant — Loocor · 2026-07-30
- An MCP feedback tool could file user feature requests — but may mostly collect compliments — hermjohnson · 2026-07-30
- Factory CTO says model wars are marketing and the harness matters more — LangChain · 2026-07-30
- A Codex user says Claude Code and Opus 5 are fast enough to skip many verification loops — brandon_galang · 2026-07-30