Client ID Metadata Documents are now generally available
- Category
- Product
- Published
CIMD is now available for every Clerk application. MCP and other public OAuth clients can connect with a URL-based identity, no support request required.
Client ID Metadata Documents (CIMD) are now generally available for all Clerk applications.
A compatible client uses an HTTPS URL as its client_id. Clerk fetches the metadata document at that URL and validates the client's identity and redirect URIs. This gives MCP and other public OAuth clients a stable identity without a pre-issued client ID, client secret, or Dynamic Client Registration.
What's changed since the beta
- Available everywhere. CIMD settings now appear on the OAuth applications settings page for every application.
- Off by default. Nothing changes for your existing OAuth flows until you enable Publish CIMD support.
- Same admission controls. Explicitly allow clients by Client ID URL, choose their scopes, review implicitly allowed clients, and set Client admission to Pre-registered clients only to restrict flows to clients you've reviewed.
Get started
- In the Clerk Dashboard, navigate to the OAuth applications settings page.
- Under Client onboarding, enable Publish CIMD support to publish CIMD in your authorization server metadata.
- Optionally, set Client admission to Pre-registered clients only and add the clients you trust from the Applications tab.
Read Manage OAuth clients with Client ID Metadata Documents for the full guide, including metadata requirements, PKCE, and client admission policies.