OAuth 2.0 Authorization Server Metadata
What is OAuth 2.0 Authorization Server Metadata?
OAuth 2.0 Authorization Server Metadata, defined in RFC 8414, is a JSON document an authorization server publishes at a well-known path so a client can learn its endpoints and supported features from the issuer URL alone. AdminKit's MCP server hardening checklist requires publishing this metadata for exactly that reason.
By AdminKit team, Netbase JSC · Updated
OAuth 2.0 Authorization Server Metadata, defined in RFC 8414 (current document status at its IETF Datatracker entry), is a JSON document an authorization server publishes, conventionally at a well-known path derived from its issuer URL, listing the endpoints and capabilities a client needs to use it: the authorization_endpoint and token_endpoint URLs, its jwks_uri, which grant types and PKCE code_challenge_methods it supports, and its registration_endpoint if it accepts Dynamic Client Registration. Rather than a client developer hardcoding each of these values after reading a provider’s documentation, a client that already knows only the issuer’s base URL can fetch this one document and configure itself against whatever that specific server actually supports, which matters most when a client is expected to work with authorization servers it has never been configured for in advance. The oauth.net summary of Authorization Server Metadata notes the practical split in paths: OpenID Connect servers publish a compatible document at /.well-known/openid-configuration, while OAuth-only servers use /.well-known/oauth-authorization-server. The format closely mirrors OpenID Connect Discovery’s provider metadata, generalized by the IETF for plain OAuth 2.0 rather than tied to OpenID Connect specifically. The MCP authorization specification requires an MCP server’s authorization server to publish this metadata for exactly that reason: a general-purpose MCP client discovers which authorization server protects a given MCP server from its OAuth 2.0 Protected Resource Metadata, then needs this document to actually complete a flow against an authorization server it’s never talked to before.
OAuth 2.0 Authorization Server Metadata is part of AdminKit’s AI agents & MCP cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does OAuth 2.0 Authorization Server Metadata let a client do?
Configure itself against an authorization server it already knows only the issuer URL for, by fetching one JSON document listing its endpoints and supported features.
What does the metadata document typically include?
The authorization_endpoint and token_endpoint URLs, the jwks_uri, supported grant types and PKCE methods, and the registration_endpoint if Dynamic Client Registration is supported.
Where is Authorization Server Metadata conventionally published?
At a well-known path derived from the authorization server's issuer URL.
Why does MCP require authorization servers to publish this metadata?
So a general-purpose MCP client can discover how to complete an OAuth flow against an authorization server it has never talked to before.