MCP just went stateless. Here's what the new roadmap builds next.
The Model Context Protocol team published an updated roadmap this week, and it's worth reading beyond the headline. The previous roadmap from March targeted four areas: transport evolution, agent communication, governance, and enterprise readiness. They delivered on all four. The changes landed in the 2026-07-28 spec release — and the biggest one is architectural. "Protocol-level sessions and the…
The Model Context Protocol (MCP) team has announced a new roadmap, which has resulted in the MCP protocol being declared "stateless". This update entails significant architectural changes, including the removal of protocol-level sessions and the initialization handshake, enabling servers to scale horizontally without retaining client state.
This transition marks a shift from being an "interesting protocol" to a "just another HTTP workload" that can run anywhere. Key changes include the default stateless and sessionless configuration, facilitating trivial horizontal scaling. Additionally, the roadmap prioritizes five areas: agentic messaging primitives, HTTP-native transport unification, agent identity, improved primitives, and developer experience.
These enhancements aim to address issues such as stateless server deployment, unified transport models, agent-to-agent authorization, efficient tool catalog management, and an improved SDK developer experience.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
