Stateless: The Future of MCP Transports

This blog post from the Agentic AI Foundation (AAIF) summarizes a talk by Shaun Smith (Hugging Face) and Kurtis Van Gent (Google Cloud) at the MCP Dev Summit North America 2026 about making the Model Context Protocol stateless. The motivation comes from operational scale: Google Cloud supports MCP servers for AlloyDB, Spanner, Cloud SQL, Bigtable, and Firestore, while Hugging Face runs over 2,500 MCP servers via Spaces and manages over 20 million tool calls across 40+ databases in a single month, with a single tool call generating over 100 MCP protocol messages. The core problem is that MCP is currently stateful, requiring initialization handshakes and persistent session context, which breaks down behind load balancers where requests can arrive at any server. The proposed solutions include: SEP-1442 (removing the initialization handshake as a required first step, folding protocol negotiation into the first actual request like tools/list), SEP-2322 (fixing elicitation by making it a sequence of independent requests where state travels in the payload rather than requiring coordinated servers), moving toward a session-free protocol by default with explicit resource handles passed as tool call parameters, and SEP-2243 (HTTP standardization mirroring JSON-RPC fields into HTTP headers so load balancers can route without parsing payloads). The transport changes are on track for the June spec release, with SEPs landing in April followed by two months of SDK implementation. Future work includes eTags for resource freshness, TTL hints on tool lists, and pluggable transports for WebSockets and gRPC. The working group operates under the Agentic AI Foundation. 

https://aaif.io/blog/stateless-the-future-of-mcp-transports/

Comments

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

SecObserve: Simplified Vulnerability and License Management for CI/CD Pipelines

Secure Vibe Coding Guide: Best Practices for Writing Secure Code