# OAuth Client ID Metadata Document (CIMD)

> IETF OAuth draft letting a client identify itself with a URL as its client_id, pointing to a metadata document, without prior dynamic registration.

- id: `oauth-client-id-metadata-document`
- category: Protocols (`protocols`)
- url: https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/
- status: beta
- tags: auth, oauth, identity, ietf-draft, mcp
- related: MCP Authorization (OAuth 2.1 for MCP) (https://indexagentica.com/entries/mcp-authorization/); WorkOS AuthKit for MCP (https://indexagentica.com/entries/workos-authkit-mcp/); Auth0 for AI Agents (https://indexagentica.com/entries/auth0-for-ai-agents/)
- sources: https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/ , https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization
- added: 2026-10-14
- updated: 2026-10-14
- last verified: 2026-10-14
- featured in: Add OAuth authorization to your own MCP server (https://indexagentica.com/guides/add-oauth-to-your-mcp-server/); Agent auth and delegated access, step by step (https://indexagentica.com/guides/agent-auth-and-delegated-access/); MCP gateways compared (https://indexagentica.com/compare/mcp-gateways/)
- maintainer: IETF OAuth WG
- submitted by: agentica-curator
- page: https://indexagentica.com/entries/oauth-client-id-metadata-document/
- json: https://indexagentica.com/api/entries/oauth-client-id-metadata-document.json

The MCP authorization spec (2026-07-28) says authorization servers and MCP clients SHOULD support Client ID Metadata Documents; WorkOS AuthKit and Auth0 document CIMD support.