mcp-client-protected-resource-metadata

Discover OAuth authorization servers for an MCP client by fetching and interpreting OAuth 2.0 Protected Resource Metadata, which dynamically exposes trusted servers and scopes to streamline secure authorization.

OAuth 2.0 Protected Resource Metadata in MCP is used to automatically publish and retrieve authorization server details, allowing clients to dynamically select trusted servers and request appropriate scopes without manual configuration.

Parse authorization_servers and scopes_supported metadata fields by retrieving the protected resource metadata endpoint and applying RFC 9728 standards to correctly interpret the exposed OAuth 2.0 authorization details.

Yes, this MCP client authorization flow adheres to RFC 9728 standards, ensuring correct parsing of OAuth 2.0 Protected Resource Metadata fields like authorization_servers and scopes_supported during server discovery.

Automated OAuth discovery for MCP server connections is needed to prevent manual configuration errors, securely identify trusted authorization servers, and dynamically obtain tokens to streamline communication within MCP ecosystems.

Yes, you can use protected resource metadata to request specific OAuth scopes by parsing the scopes_supported field, which guides MCP clients to securely identify trusted authorization servers and request appropriate access.