Repository navigation
[FEATURE]: Support for MCP Support Client ID Metadata Document (CIMD) #25961
Description
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
Reacted by Rishab Dalai, Réda Housni Alaoui, oleduc-pokainc, Adam Kaczmarek, Leonid Tsarev, Paul Irwin, Valentin Delaye, Nico, Josef Kolář, Nate Meyer and 7 more
Metadata
Metadata
Assignees
Labels
No labels
Activity
oleduc-pokainc commentedon Jul 7, 2026
Is this planned for a specific release?
bart-westenenk-bex commentedon Jul 30, 2026
This is now the new standard. When is this planned to be implmeentd?
jonesbusy commentedon Jul 30, 2026
For reference MCP inspector 2.0 also implemented CIMD (but we need to provide the metadata ourself)
MerryOscar commentedon Sep 3, 2026
any updates on this?
rekram1-node commentedon Sep 22, 2026
Implemented on V2. When the authorization server advertises
client_id_metadata_document_supportedand accepts public clients, login useshttps://opencode.ai/oauth/opencode/client.jsonas theclient_idand skips dynamic registration entirely. Servers without CIMD support fall back to DCR, and a configuredoauth.client_idstill takes priority over both. SeeCLIENT_METADATA_URLinpackages/core/src/mcp/oauth.ts.kingds commentedon Oct 15, 2026
Hi, I'd like to request that you update your docs to reflect this change, https://opencode.ai/v2/docs/mcp-servers still says that dynamic client registration will be used with no mention of CIMD.
rekram1-node commentedon Oct 15, 2026
Yup will do