Overview
This article will answer two frequently asked questions about Auth0 and Model Context Protocol (MCP).
Applies To
- Model Context Protocol (MCP)
- Frequently Asked Questions
Solution
After the dynamic client registrations, does Auth0 have some inherent logic to clean these dynamically created client IDs at regular intervals?
Auth0 does not currently have such a capability. Dynamic Application Registration is being analyzed for evolution, however, and this feature will likely be improved in the future.
Is it feasible to host a custom .well-known/openid-configuration JSON file externally (i.e., not on an Auth0 custom domain)? The endpoints within the file—such as “authorization_endpoint”: “https://CUSTOM_DOMAIN/authorize”—would still point to Auth0, but the file itself would reside at a custom URL. The intent is to provide a custom application registration URL, allowing greater control over how SPA clients that are provisioned and managed for MCPs are managed and their lifecycle.
Yes, this is possible.