Create and manage MCP registries
An MCP registry is a container registry that the platform can pull MCP server images from.
Each registry has an authority, such as registry.example.com:443, and the credentials to pull from it.
Adding a registry does not deploy an MCP server.
Access
You need permission to manage MCP infrastructure on the platform. The same permission manages the MCP catalog and private networks. Permission to manage external MCP servers is separate and does not give access to registries.
Under Manage platform, open MCP Servers, then select the Registries tab.
Management source
The Management source column shows where each registry comes from:
- Installation: The platform reads these registries from the image registry credentials set at
installation (
imageRegistries.cmApps.auth, see the CM Platform Deployment Guide). The list shows one registry for each registry host that has a credential there. To change these registries, change the installation. The portal cannot change or delete them. - Portal: Created in the portal. The platform keeps each portal registry and its credentials in a Kubernetes Secret that it manages.
Create a registry
Select Create registry and complete these fields:
- Display name: The name shown in the portal and in registry pickers.
- Authority: The registry hostname and an optional port, such as
registry.example.com:443. Do not include a scheme, path, or query. - Username: The user that pulls from the registry. The username cannot contain a colon.
- Password or token: The password or access token of that user.
Every portal registry needs a username and a password or token. The portal sends both exactly as you enter them, including spaces.
You cannot change the authority after you create the registry. To use a different authority, create another registry.
Change a registry
Open a portal registry to rename it. To set a new username and password or token, select Replace credentials. The new credentials replace the stored credentials.
The portal never shows stored credentials.
If a change fails and the portal cannot confirm the result, open the registry again before you submit another change.
Delete a registry
Open a portal registry, select Delete, and confirm.
The platform removes the registry and its credentials. The platform refuses to delete a registry that is still in use:
- A catalog entry uses it. Change that entry to use another registry first.
- An MCP deployment pulls its image with the registry's credentials. Delete that deployment first. A stopped deployment counts too, because it pulls the image again when it starts.
You cannot delete an installation registry in the portal.