# Dynamic Client Registration & Client ID Metadata

[3 · Permit](/category/permit/)

| Dynamic Client Registration & Client ID Metadata |
| --- |
| Category | [Permit](/category/permit/) |
| Also known as | RFC 7591, Client ID Metadata Document, DCR |
| Related | [Model Context Protocol](/protocols/mcp/), [OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)](/protocols/oauth-metadata-for-agents/) |

[Permit](/category/permit/) Dynamic Client Registration (DCR, RFC 7591) and OAuth Client ID Metadata Documents allow an AI agent or MCP host to authenticate with a newly discovered authorization server without a human developer manually pre-registering a client_id on that site first. In the MCP Authorization specification (2026-07-28), an agent host can present an HTTPS URL as its client_id pointing to a JSON metadata document it controls (Client ID Metadata Document) or register dynamically via RFC 7591 after discovering endpoints through RFC 9728 Protected Resource Metadata. Used by: mcp, oauth-metadata-for-agents.

## Instances

Not applicable.

## See also

- [Model Context Protocol](/protocols/mcp/)
- [OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)](/protocols/oauth-metadata-for-agents/)

## References

- [https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/client-registration](https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization/client-registration) (2026-07-28) VERIFIED
- [https://www.rfc-editor.org/rfc/rfc9728](https://www.rfc-editor.org/rfc/rfc9728) (2026-09-05) VERIFIED

[JSON](/terms/dynamic-client-registration/index.json) · [Markdown](/terms/dynamic-client-registration/index.md) · [OKF v0.2](/okf/terms/dynamic-client-registration.md)