An updated roadmap lays out five concrete priorities to evolve the Model Context Protocol for modern, agent-driven workloads: agentic messaging primitives, HTTP-native transport unification and hardening, agent identity and enterprise-ready security, improved primitives, and a better SDK developer experience. Work on agentic messaging focuses on long-running loops, server-pushed streamed results, steering in-flight work, Tasks (maturing SEP-2663), subscriptions/listen, progress notifications, and server-initiated events (webhooks/channels) with a composition review across Agents, Transports, and Triggers & Events working groups. Transport work builds on the recent release that makes remote MCP servers standard HTTP workloads, aiming to unify deployments (including Streamable HTTP over stdio) to simplify hosting and client/server development.
Security and identity work shifts MCP away from human-browser approvals toward standardized agent identities for cloud workloads: adopting Demonstrating Proof of Possession (DPoP), Workload Identity Federation, the ID-JAG grant for Enterprise-Managed Authorization, and standard token exchange, while engaging OAuth/IETF and WIMSE groups. Primitive improvements target clearer tool-calling result contracts and progressive discovery to avoid paying the cost of huge tool catalogs upfront. SDK efforts prioritize ergonomics, spec conformance, and docs across languages. Specification Enhancement Proposals aligned with these areas get expedited review; contributors are invited to join working groups, file or comment on SEPs, use SEP-2133 for experimental extensions, or contribute code and docs.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.