OAuth Client ID Metadata Document Support in MCP Clients

Security Recommendation

Authorization servers and MCP clients SHOULD support OAuth Client ID Metadata Documents. This mechanism allows MCP clients to present their identity and configuration to authorization servers without requiring pre-registration.

What It Provides

Client ID Metadata Documents allow:

• Clients to self-describe their configuration (redirect URIs, grant types, etc.)
• Authorization servers to validate client properties without prior registration
• A standardized way for clients to present their identity

How It Works

The MCP client hosts a metadata document at a URL that serves as its client_id. The authorization server fetches this document to learn about the client's configuration.