What parts of OAuth 2.1 does MCP use?
In short: MCP authorization uses OAuth 2.1, which folds a decade of OAuth security advice into one baseline. For MCP that means PKCE, protected resource metadata and tokens bound to their audience. Since 2026-07-28 it also means issuer validation per RFC 9207. Gateways should enforce all four.
What does OAuth 2.1 change from OAuth 2.0?
It requires PKCE for authorization code flows, drops the implicit grant and the password grant, and requires exact redirect URI matching.
Which parts does MCP lean on?
Protected resource metadata tells clients which authorization server to use. Audience binding stops a token minted for one server working on another.
Issuer validation stops a client being tricked into sending a code to the wrong authorization server.
What should a buyer ask a gateway vendor?
Ask whether the gateway validates audience on every call, rejects tokens meant for other services and supports CIMD clients. Our RFP checklist lists these questions.
Sources
- MCP spec: Authorization [mcp-auth] read 2026-11-03
- MCP blog: 2026-07-28 release [mcp-0728] read 2026-11-03
Other explainers are listed on the spec hub.
By The Datasheet desk · Published and reviewed 2026-11-03