Register an MCP Client from Its Metadata Document
Register an MCP client from its Client ID Metadata Document (CIMD) when its vendor publishes one. The client's ID is an HTTPS URL on the vendor's domain, and that URL serves the client's name, redirect URIs, and how it authenticates. You review what the document declares, and ThunderID creates the application from it. You do not enter redirect URIs or credentials yourself.
ThunderID reads the document only when you register or re-fetch the client. When a user signs in, the client authenticates like any other application.
Prerequisites
- ThunderID is running. See Get Started.
- You can sign in to the ThunderID Console.
- For a client without a tile in the Console, its metadata document URL.
Start the Application Wizard
- Sign in to the ThunderID Console.
- Navigate to Applications and click Add Application.
- Select MCP Client.
- If prompted, select an organization unit and click Continue.
Choose the Client
On Which MCP client are you connecting?, do one of the following:
- For Claude, ChatGPT, or Visual Studio Code, click its tile. ThunderID creates the application straight away and opens it.
- For any other client, select Another client with a CIMD, enter its document URL, and click Fetch document. Review the preview, click Continue, adjust the name on the Details step if needed, and click Finish.
Review and Update the Client
Open the application's General tab. A CIMD section shows the values taken from the document, read-only. Configure everything else, such as allowed user types and the sign-in flow, as you would for any other application.
When the vendor changes its document, ThunderID does not pick up the change on its own. Click Re-fetch document, review the changes, click Apply, and then Save.
Next Steps
- MCP Client Identity: Why metadata documents exist, and how they compare with configuring a client manually and Dynamic Client Registration.
- Configure an MCP Client Manually: Configure a client by hand when it does not publish a metadata document.
- Secure Your MCP Server: Protect the MCP server these clients connect to.
