{"slug": "mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next", "title": "MCP just went stateless. Here's what the new roadmap builds next.", "summary": "The Model Context Protocol team published an updated roadmap and a new spec release that removes protocol-level sessions and the initialization handshake, enabling servers to scale horizontally without holding state. The roadmap outlines five focus areas, including agentic messaging primitives, HTTP-native transport unification, agent identity, improved primitives, and SDK developer experience, with dedicated working groups for each.", "body_md": "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.\n\nThe changes landed in the [2026-07-28 spec release](https://modelcontextprotocol.io/specification/2026-07-28/changelog) — and the biggest one is architectural.\n\n\"Protocol-level sessions and the initialization handshake are gone, so a server can scale horizontally without holding state.\"\n\nThat's not a minor tweak. That's MCP crossing from \"interesting protocol\" to \"just another HTTP workload you can run anywhere.\"\n\n`server/discover`\n\nFive areas, each with dedicated Working Groups:\n\n**Agentic messaging primitives** — server-initiated events (webhooks and channels, so clients stop polling), plus maturing Tasks into the core spec. The goal: MCP handles long-running agentic loops natively.\n\n**HTTP-native transport unification** — unify stdio and Streamable HTTP under one transport model. A local MCP server and a cloud-hosted one should behave identically.\n\n**Agent identity** — this is the one worth watching. Today auth is built around a human approving in a browser. That doesn't work for agent-to-agent calls or unattended cloud workloads. The roadmap targets DPoP, Workload Identity Federation, and standard token exchange — with active engagement in IETF OAuth and WIMSE standards bodies.\n\n**Improved primitives** — two specific problems: `tools/call`\n\nresponses can carry output in multiple forms with no contract for which one clients use, and large tool catalogs (100+ tools) waste context tokens before a user asks anything. Progressive discovery is the proposed fix.\n\n**SDK developer experience** — conformance testing, better docs, making it easier to build MCP clients and servers whether you're writing the code yourself or pointing an agent at the libraries.\n\nThe full roadmap is at [modelcontextprotocol.io/development/roadmap](https://modelcontextprotocol.io/development/roadmap).\n\n*✏️ Drafted with KewBot (AI), edited and approved by Drew.*", "url": "https://wpnews.pro/news/mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next", "canonical_source": "https://dev.to/thegatewayguy/mcp-just-went-stateless-heres-what-the-new-roadmap-builds-next-2jdp", "published_at": "2026-08-26 08:06:48+00:00", "updated_at": "2026-08-26 08:44:56.182520+00:00", "lang": "en", "topics": ["ai-agents", "ai-infrastructure", "developer-tools", "ai-policy"], "entities": ["Model Context Protocol", "IETF", "WIMSE", "KewBot", "Drew"], "alternates": {"html": "https://wpnews.pro/news/mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next", "markdown": "https://wpnews.pro/news/mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next.md", "text": "https://wpnews.pro/news/mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next.txt", "jsonld": "https://wpnews.pro/news/mcp-just-went-stateless-here-s-what-the-new-roadmap-builds-next.jsonld"}}