MCPロードマップ2026【長時間タスクとエージェント認証が重点】

"It sets the direction for protocol work over the coming months and was developed by the Core Maintainers together with our community of maintainers and Working Groups."／"The new roadmap is organized into five priority areas."／"Each area has a set of Core Maintainers responsible for it and one or more Working Groups."／"Specification Enhancement Proposals (SEPs) that fall within these priority areas get expedited review and have the best chance of acceptance. Proposals outside them aren’t rejected automatically, but maintainer review time is scarce and goes to these areas first."（冒頭リード／Priority areas／Proposal prioritization 節）— Model Context Protocol Blog より

"The previously published roadmap came out in March with four priority areas: transport evolution and scalability, agent communication, governance maturation, and enterprise readiness."／"We’ve made significant progress in all of these over the past five months. The bulk of the changes landed in the 2026-07-28 specification release"／"Tasks were reworked based on early adopter feedback - we moved them into an official extension (SEP-2663)."／"One of the biggest changes we shipped is that protocol-level sessions and the initialization handshake are gone, so a server can scale horizontally without holding state (SEP-2575, SEP-2567)."（Looking back 節）— Model Context Protocol Blog より

"Modern agentic workloads no longer fit the standard request-and-response pattern. Loops can run for longer, servers can push streamed results, and there is a clear need to steer work mid-flight. MCP has been growing to meet these requirements, introducing Tasks, subscriptions/listen, and progress notifications."／"The work here spans server-initiated events (webhooks and channels, so clients aren’t left polling for results), a composition review across the Agents, Transports, and Triggers & Events Working Groups, and maturing the Tasks extension (SEP-2663) so it can move into the specification."（Agentic messaging primitives 節）— Model Context Protocol Blog より

"With the 2026-07-28 release, a remote MCP server is now no different from any other HTTP workload, making it easy to host and operate one on any infrastructure that developers and organizations already use for their APIs and services."／"This approach has proven to scale, and we want to stretch it to cover other deployment modes as well, including local servers speaking Streamable HTTP over stdio."（HTTP-native transport unification and hardening 節）— Model Context Protocol Blog より

"Tool calling is the part of MCP most developers touch first, and it has held up well over the lifetime of the protocol."／"A tools/call response can carry the same output in more than one form, and a server developer today has no way to know which form a given client will put in front of the model. We aim to make this easier by standardizing on one clear contract."／"Connecting to a server with a hundred tools means the model pays for that entire surface before the user has asked a single question, and tool selection tends to get worse as the list grows."／"We’re starting a progressive discovery effort so a server can offer a small entry point and reveal more of its catalog as the conversation narrows."（Improved primitives 節）— Model Context Protocol Blog より

"MCP authorization today is built around a person approving access in a browser. That works well for interactive clients, but more and more of the callers are agents running as cloud workloads with their own identity, acting on behalf of a user who isn’t present, or delegating narrower authority to sub-agents."／"We want MCP servers to have a standardized way to recognize and trust those agent identities, built on existing standards rather than pasted API keys and long-lived tokens."（Agent identity and enterprise-ready security 節）— Model Context Protocol Blog より

"The work here covers finalizing Demonstrating Proof of Possession (DPoP) and driving its adoption, and defining an opinionated path for agent identity and delegation through Workload Identity Federation, the ID-JAG grant behind Enterprise-Managed Authorization, and standard token exchange."／"We will also continue to grow our engagement with the OAuth standards bodies, including the IETF OAuth and WIMSE working groups, to help the underlying standards evolve with the building blocks that agent identity needs."／"Our SDKs are how developers experience MCP."／"We are investing in their ergonomics and their conformance with the specification, and in making them intuitive and well-documented across every platform and language we support."（Agent identity and enterprise-ready security／Improved SDK developer experience 節）— Model Context Protocol Blog より