The Model Context Protocol published a new roadmap on August 22 that names its authorization model as a core problem: the spec assumes a human clicking approve in a browser, while the callers showing up in production are cloud agents and sub-agents with no human anywhere in the loop. The fix list is explicit and unusually concrete for a roadmap document, covering proof-of-possession tokens, workload identity federation, the ID-JAG grant behind enterprise-managed authorization, and standardized token exchange. The roadmap post frames the whole document as current thinking rather than firm commitments.
Key facts
- Five priority areas: agentic messaging primitives, HTTP-native transport unification, agent identity and enterprise security, improved primitives, and SDK automation.
- Published August 22, 2026, as the sequel to the July 28 spec that removed sessions and the initialize handshake from the protocol core.
- The Hacker News thread had 174 points and 127 comments when checked, with the top comments sharply critical.
- Primary source: the roadmap post and the roadmap page.
Start with the security problem, because it is the one with teeth. A bearer token works like a movie ticket: whoever holds it gets in, and the door does not care who bought it. That is acceptable when a person authorized the ticket a moment ago in a browser they control. It is much less acceptable when the ticket is handed from an orchestrator to a sub-agent to a tool server across three networks, because any intermediary that sees it can replay it. A May 2026 issue on the MCP repository laid out the case in detail: no cryptographic client binding means replayability, request tampering, intermediary exposure, and weak client identity. Proof of possession is the standard answer, and it is the equivalent of stamping the ticket with the holder's fingerprint so a stolen one is useless.
This matters more as agent systems get deeper. When an agent spawns sub-agents that call tools that call other tools, every hop is a place where authority can be forwarded further than intended. That is the same structural weakness behind the self-propagating prompt injection Ground Truth covered, and it is why sandboxing AI agents has become its own discipline. Cloudflare's approach of never handing an agent a key at all is the same instinct expressed as architecture rather than protocol.
The transport half of the roadmap is quietly more ambitious than it reads. MCP wants Streamable HTTP semantics to become the single binding for every server, including local ones, which it describes as HTTP over stdio. The goal is to stop local and remote MCP from diverging into two dialects that need separate handling in every client. Alongside that come caching mechanics that go past simple time-to-live rules into deterministic tool ordering and ETags on tool-call results, plus explicit capability scoping now that the protocol no longer keeps sessions. There is also an effort to make three different "the server is not done yet" patterns compose properly: Tasks, subscriptions, and progress notifications currently have separate lifecycles, cancellation semantics, and error surfaces.
Context for why this is happening now: the breaking change already landed. The July 28 specification removed the initialize handshake and session header from the core, moved client metadata into a per-request field, made discovery optional, and pushed Tasks out into an extension, as Ground Truth covered when MCP dropped the handshake. The August roadmap is the cleanup crew. You can see the migration cost in the bug tracker: MCP Inspector currently omits a now-required header on task calls over Streamable HTTP, which makes strict servers reject the requests outright.
Governance has moved too, and the shift is easy to miss. Anthropic donated MCP to the Agentic AI Foundation under the Linux Foundation in December 2025. The governance documentation now describes named lead and core maintainers plus working groups, with membership attached to individuals rather than companies. Anthropic still participates heavily; it no longer holds formal unilateral control. The roadmap also does something structurally important that nobody is discussing: proposals aligned with the five priority areas get expedited review. That turns the document from a description of the future into a mechanism that allocates maintainer attention, which means process is now as load-bearing as any single feature.
The honest caveat is that the community is not sold. The Hacker News thread is genuinely split. Supporters say the stateless rewrite makes gateways and registries far easier to operate. The sharpest critics say MCP is overengineered, that statefulness was the original sin, that HTTP is a questionable choice for a universal local IPC bus, and that plain REST plus a skills file plus ordinary OAuth would have covered most real cases without any of this. None of that is settled by a roadmap. What the roadmap does settle is that MCP intends to become production infrastructure, with the migration bills that implies.
Originally published on Ground Truth, where every claim is checked against the primary source.
