The New MCP Roadmap

Today we’re excited to people an updated roadmap for the Model Context Protocol (MCP), covering the adjacent specification merchandise and beyond.

The roadmap sets the guidance for protocol activity complete the coming months. It was developed by the Core Maintainers together pinch our organization of maintainers and Working Groups.

Explore the roadmap →

Priority areas

The roadmap is organized into 5 privilege areas. Several of them prime up activity that the previous roadmap listed arsenic connected the horizon, including server-initiated events, consequence type improvements, and supplier identity, which person since matured capable to go priorities successful their ain right. Each area is owned by a group of Core Maintainers and 1 aliases much Working Groups.

Agentic messaging primitives

Modern agentic workloads nary longer fresh the modular request-and-response pattern. Loops tin tally for longer, servers tin push streamed results, and location is simply a clear request to steer activity mid-flight. MCP has been increasing to meet these requirements, introducing Tasks, subscriptions/listen, and progress notifications. We want to make judge that we not only connection the correct primitives for the job, but besides that they activity good together. The activity present spans server-initiated events (webhooks and channels, truthful clients aren’t near polling for results), a creation reappraisal crossed the Agents, Transports, and Triggers & Events Working Groups, and maturing the Tasks hold (SEP-2663) truthful it tin move into the specification.

HTTP-native carrier unification and hardening

With the 2026-07-28 release, a distant MCP server is now nary different from immoderate different HTTP workload, making it easy to big and run 1 connected immoderate infrastructure that developers and organizations already usage for their APIs and services. The exemplary has proven to scale, and we want to agelong it to screen different deployment modes arsenic well, including section servers speaking Streamable HTTP complete stdio. Unifying connected 1 carrier lets america simplify MCP server and customer improvement moreover further.

Agent personality and enterprise-ready security

MCP authorization coming is built astir a personification approving entree successful a browser. That useful good for interactive clients, but much and much of the callers are agents moving arsenic unreality workloads pinch their ain identity, acting connected behalf of a personification who isn’t present, aliases delegating narrower authority to sub-agents. We want MCP servers to person a standardized measurement to admit and spot those supplier identities, built connected existing standards alternatively than pasted API keys and long-lived tokens.

The activity present covers finalizing Demonstrating Proof of Possession (DPoP) and driving its adoption, and defining an opinionated way for supplier personality and delegation done Workload Identity Federation, the ID-JAG assistance down Enterprise-Managed Authorization, and modular token exchange. We will besides proceed to turn our engagement pinch the OAuth standards bodies, including the IETF OAuth and WIMSE moving groups, to thief the underlying standards germinate pinch the building blocks that supplier personality needs.

Improved primitives

Tool calling is the portion of MCP astir developers touch first, and it has held up good complete the life of the protocol. Where it falls a spot short, however, is successful the consequence handling. A tools/call consequence tin transportation the aforesaid output successful much than 1 form, and a server developer coming has nary measurement to cognize which shape a fixed customer will put successful beforehand of the model. We purpose to make this easier by standardizing connected 1 clear contract.

The different situation we request to reside for primitive usage is their ever-growing scale. Connecting to a server pinch a 100 devices intends the exemplary pays for that full aboveground earlier the personification has asked a azygous question, and instrumentality action tends to get worse arsenic the database grows. We’re starting a progressive find effort truthful a server tin connection a mini introduction constituent and uncover much of its catalog arsenic the speech narrows.

Improved SDK developer experience

Our SDKs are really developers acquisition MCP. We are investing successful their ergonomics and their conformance pinch the specification, and successful making them intuitive and well-documented crossed each level and connection we support. This is moreover much important now that galore developers build MCP clients and servers by pointing an supplier astatine our libraries, wherever clear APIs and meticulous docs determine whether the codification will activity pinch minimal friction.

Proposal prioritization

Specification Enhancement Proposals (SEPs) that autumn wrong these privilege areas get expedited reappraisal and person the champion chance of acceptance. Proposals extracurricular them aren’t rejected automatically, but maintainer reappraisal clip is scarce and goes to the roadmap first.

If you’re considering a SEP, place the privilege area it belongs to, raise it pinch the applicable Working Group, and activity pinch its members to style your proposal. Each area connected the roadmap names the Core Maintainers responsible for it, and anyone willing successful contributing tin scope them connected Discord. We’re excited to activity pinch the organization to reappraisal and build connected the proposals that support this roadmap.

Get involved

Every privilege area supra has a Working Group down it aliases forming astir it, and each of them person room for much contributors. There are respective ways to participate:

• Join a Working Group aliases Interest Group: spot the Working and Interest Groups page and the community channels.
• Propose aliases remark connected a SEP: publication the SEP guidelines, past unfastened 1 aliases measurement in.
• Start an experimental extension: SEP-2133 lets immoderate WG aliases IG research successful an experimental-ext- repository earlier a general SEP.
• Contribute directly: the contributing guide covers the specification, SDKs, and tooling.

We look guardant to increasing and evolving MCP together!