Computing Life · Share · YageAug 28, 2026, 08:00 UTC+8

MCP's two-year shift: the default caller moves from a human at a screen to a cloud-side process

从屏幕前的人到云端的进程：MCP 默认调用者的两年转向

MCP maintainers published a new roadmap on Aug 22, listing agent identity as one of five priorities. The shift moves authorization away from a human clicking approve in a browser and toward cloud agents that carry their own identity and obtain tokens autonomously. The path started with OAuth 2.1 in March 2025, added machine-to-machine credentials in November 2025, and introduced the Workload Identity Federation proposal WIF in December 2025. The cost: the July 2026 spec removed session headers, mandated self-contained requests, and deprecated the recently added Sampling and Roots capabilities. The chokepoint moves from personal API keys to the cloud platform and enterprise IdP that issue tokens. WIF and DPoP are still drafts; ID-JAG remains an IETF draft. The HN thread scored 269 points, with over-engineering criticism taking up a fair share of the discussion.

Why it matters: MCP roadmap elevating agent identity to a priority is a key signal of the protocol's shift from local scripts to unattended cloud workloads. The article traces the two-year evolution with concrete dates and changelog references — good information density. Deduction: this is a ...

Read the original ↗Export Markdown

Take

This piece connects two years of scattered MCP auth changes into a single arc: OAuth 2.1 for remote calls in March 2025, machine-to-machine credentials in November 2025, the WIF proposal in December 2025 for platform-issued short-lived JWTs, and the ID-JAG draft in May 2026 for apps to get tokens on a user's behalf without a browser popup. The August 22 roadmap makes it official: MCP's default caller is no longer a human at a screen, but a cloud process that needs to obtain its own authorization.

The costs are concrete. The July 2026 spec removed session headers and mandated self-contained requests—every existing implementation needs updating. More directly, MCP deprecated two capabilities it had only added in November 2025: Sampling (server borrowing the client model) and Roots (client sharing local files with the server). Dropping them after eight months signals that the personal-developer, single-machine use case is no longer the priority.

The chokepoint shift is worth sitting with. Before, you managed your own API keys—lose one, rotate it. Now authorization concentrates at the cloud platform and enterprise IdP, where token issuance, revocation, and policy evaluation happen. The upside is zero-trust and short-lived credentials. The downside is your control depends on how well the platform and IdP implement these mechanisms. WIF and DPoP are still drafts; ID-JAG is an IETF draft. Don't read this as finished work. The HN thread scored 269 points with a fair amount of over-engineering criticism—I'd discount the readiness level a bit. The protocol is heading enterprise, but the construction isn't done.

Source: Computing Life · Share · Yage · yage.ai
Published: Aug 28, 2026, 08:00 UTC+8 · Aug 28, 2026