MCP 2026-07-28 Specification: Transport Going Stateless for Scalable Agents
We are releasing the MCP 2026-07-28 specification, transforming the protocol from stateful to stateless to boost reliability and scalability. This update removes session handshakes, enabling requests to land on any server instance behind a load balancer. We also introduce Multi Round-Trip Requests, cacheable list responses, and hardened authorization standards. Major SDKs for TypeScript, Python, Go, and C# now support these changes, marking a significant step toward production-grade infrastructure for agentic workflows.
This release is the clearest signal yet that MCP is becoming real production-grade infrastructure.
- punkpeye
Finally.
I am running an MCP server gateway/registry (some of you may know Glama).
I cannot tell you what portion of our issues/bugs were due to the need to persist server state.
This change will allow us to offer a lot easier way for people to use Open-Source MCP servers.
- dend
Hey folks - one of the Lead Maintainers for MCP. Happy that we got this release out the door today, this is an exciting change for those that wanted to roll out remove MCP servers into serverless hosts. There is, of course, more good stuff packed, so if you have questions or feedback - our team is here to help!
- btbuilder
Excellent improvement. The server-side complexity required to handle sessions has been a large burden both on infrastructure and on educating teams on its characteristics.
- rupertsworld
I'm currently working on getting all my MCP tools ported over to HTTP, with a single call_http tool, so I can just call APIs and benefit from a long history of patterns (like stateless-ness) that have already existed there for decades.
- osinix
This is the right practice. Why put the burden on the server? It is the job of client to remember, not the server. Server is there to serve requests, not do the remembering. That is how http worked from the beginning and that is why it has been successful.