Remote MCP servers that use the spec's authorization protect their tools with OAuth 2.1: the server is a protected resource, advertises its authorization server through protected resource metadata, and accepts only tokens issued for itself. Local stdio servers use other credentials. The 2026-07-28 revision prefers Client ID Metadata Documents and requires issuer validation. Mistakes cause token passthrough and confused deputies.
Read in this order
- OfficialUnderstanding Authorization in MCP (tutorial)Start here: a tutorial walking through the MCP authorization flow end to end.
- OfficialAuthorization (MCP specification)The normative rules a compliant server and client must follow.
- OfficialRFC 9728: OAuth 2.0 Protected Resource MetadataThe standard behind how a server tells clients which authorization server to use.