Feature hasn't been suggested before.

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

For authorization server that support Support Client ID Metadata Document (CIMD) (Like keycloak https://www.keycloak.org/securing-apps/mcp-authz-server)

MCP clients and authorization servers SHOULD support OAuth Client ID Metadata Documents as specified in OAuth Client ID Metadata Document. This approach enables clients to use HTTPS URLs as client identifiers, where the URL points to a JSON document containing client metadata. This addresses the common MCP scenario where servers and clients have no pre-existing relationship.

Other MCP client (Claude, VSCode are already supporting it). Their respective metadata is hosted at

• https://vscode.dev/oauth/client-metadata.json
• https://claude.ai/oauth/claude-code-client-metadata

For reference

• https://client.dev/
• https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/
• https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#client-id-metadata-documents