MCP maintainers publish a roadmap with five priority areas for the protocol

On August 22, 2026, MCP lead maintainers David Soria Parra and Den Delimarsky published a Model Context Protocol roadmap with five priority areas, after the 2026-07-28 specification shipped. It gave no date for the next specification release.

Archive entry: this covers an event from August 22, 2026, and we published it on November 8, 2026. The details come from sources dated at the time and may have changed since.

On August 22, 2026, MCP lead maintainers David Soria Parra and Den Delimarsky published a roadmap post on the MCP blog, after the 2026-07-28 specification shipped. It set five priority areas for the Model Context Protocol and gave no date for the next specification release.

What shipped from the March roadmap

Most changes from the previous roadmap, published in March, shipped in the 2026-07-28 specification. Sessions and the handshake were removed, server/discover was added, list results became cacheable and Tasks became a formal extension (SEP-2663).

The five priority areas

The five priority areas were agentic messaging primitives, HTTP-native transport unification and hardening, agent identity and enterprise-ready security, improved primitives, and improved SDK developer experience. Specific work named in the roadmap included the following.

Agentic messaging: server-initiated events delivered through webhooks and channels, and moving the Tasks extension toward the core specification.
Transport: extending Streamable HTTP to local servers that ran over stdio, with the aim of a single transport.
Security: finalizing DPoP (RFC 9449) and a prescribed approach to agent identity and delegation using Workload Identity Federation.
Primitives: one clear contract for tool results and progressive discovery, so servers could start small and reveal more tools as a conversation narrowed.

Governance and what it meant for builders

The project formally adopted the Contributor Ladder. Working Groups triaged SEPs in their own domain, and a feature lifecycle and deprecation policy governed the specification. SEPs in the priority areas received faster review. For MCP server and client authors, the roadmap showed which protocol changes were likely to follow, including a single HTTP-based transport for local servers and one contract for tool results.

Sources

The New MCP Roadmap (Model Context Protocol, August 22, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.