Skip to main content
To access a protected MCP server, you must first register your MCP client with Auth0. Once registered, Auth0 assigns the client a unique identifier: either an Auth0-generated client ID or a domain-verified CIMD URL. Auth0 also configures the OAuth credentials required for secure authentication and authorization. You can register your MCP client with Auth0 manually or dynamically.

​
Create manually

In manual client registration, you can register any MCP client using the Auth0 Dashboard or Auth0 CLI. To learn more, read Create Applications

​
Register with CIMD

Register an MCP client in Auth0 by importing its externally hosted Client ID Metadata Document (CIMD) from a URL. Auth0 supports manual and dynamic CIMD registration. To learn more, read Register Applications with CIMD. With CIMD, you only need to register your MCP server once per deployment. All instances of that deployment use the same CIMD URL as their Client ID. Whether you’re running one instance or hundreds across multiple regions, they all share the same registration credentials. This eliminates the need to manage separate Client IDs and Client Secrets for each instance, simplifying credential management at scale.

​
Dynamic Client Registration (DCR)

Dynamic Client Registration allows an MCP client to register itself at runtime without human intervention. For production MCP deployments, we recommend using CIMD registration for its security and scalability in managing registration credentials.

​
Learn more