The New MCP Roadmap

The Model Context Protocol (MCP) has unveiled its updated roadmap for the upcoming specification release and future developments. The roadmap, crafted by Core Maintainers alongside the community of maintainers and Working Groups, outlines five priority areas that will guide the protocol's progress. Among these areas are server-initiated events, result type enhancements, and agent identity, which have advanced enough to become priorities.

One of the key focuses is on modern agentic workloads, which now demand more sophisticated communication patterns, such as loops that span longer durations and servers that push streamed results. MCP has adapted by introducing Tasks, subscriptions/listen, and progress notifications. The roadmap also underscores the need for unified server-initiated events, such as webhooks and channels, to alleviate clients from continuously polling for results.

Another significant aspect is the unification and hardening of HTTP-native transport. With the 2026-07-28 release, MCP servers now operate similarly to any other HTTP workload, allowing them to be deployed on any infrastructure commonly used for APIs and services. This unification aims to simplify development for MCP servers and clients.

Agent identity and security are also pivotal on the roadmap. MCP authorization currently relies on browser-based approval, which is less effective for cloud-based agents acting on behalf of users without direct interaction. The roadmap seeks to introduce a standardized method for recognizing and trusting agent identities, built upon existing standards rather than API keys and long-lived tokens.

This involves finalizing Proof of Possession (DPoP) and driving its adoption, as well as defining a path for agent identity and delegation through Workload Identity Federation and standard token exchange.

Additionally, the roadmap emphasizes improved tools/call response handling, aiming to standardize the contract for result forms. This is coupled with a progressive discovery effort to allow servers to offer a limited entry point and progressively reveal more of their tool catalog as the conversation narrows.

The SDK developer experience is also under scrutiny, with efforts to enhance their ergonomics, conformance with the specification, and intuitiveness across all supported platforms and languages. Proposal prioritization is another crucial element, where SEP Enhancement Proposals (SEPs) that align with the roadmap's priority areas receive expedited review.

Community involvement is encouraged in various forms, from joining Working Groups or Interest Groups, proposing or commenting on SEPs, starting experimental extensions, to directly contributing to the specification, SDKs, and tooling.