MCP authorization
Also called: MCP OAuth, protected MCP server
MCP authorization controls access to a protected server. For HTTP, the inspected 2026-07-28 revision defines an OAuth-based arrangement: the MCP server is the protected resource, an authorization server issues access tokens, and the client presents an appropriate token with each protected request. This framework is optional for MCP implementations overall.
A notes client might discover the service’s authorization server through protected-resource metadata, then obtain permission to read notes. A token for another service must not be accepted merely because it looks valid. Requested scopes should match the needed access. The HTTP flow is separate from local stdio credential handling, and the referenced OAuth 2.1 document remains a draft in this MCP revision.
- Read first
- Model Context Protocol, OAuth 2.0
- Related
- OAuth 2.0, Bearer token, MCP tool discovery
- Further reading
- MCP — authorization, revision 2026-07-28