MCP server registries
Add and manage MCP server registries so the marketplace lists every server they publish.
What is a registry?
An MCP server registry is an HTTP endpoint that implements the MCP Registry OpenAPI specification (/v0.1/servers). When you add a registry to a workspace, its servers become available through browse_plugin_catalog. A listed server uses no resources until you install it.
Inspect the catalog entry, then call install_plugin. Registries are how you discover servers. Installation is always a separate, explicit step.
Default registry
Oxagen seeds every new workspace with the Official MCP Registry:
https://registry.modelcontextprotocol.ioThe MCP project publishes this registry. It lists a broad catalog of community and vendor MCP servers. It is the workspace default at creation, and you can remove it if you do not need it.
Registries are workspace-scoped
Each workspace keeps its own registry list. Adding a registry in one workspace has no effect on other workspaces in your org. Read the registry list with list_plugin_registries.
The single-default rule
A workspace with registries has one default:
- The first registry you add becomes the default.
- If you remove the default and other registries remain, the most recently added registry becomes the new default.
- If you have exactly one registry, it is the default and you cannot change that. Add a second registry first if you need to swap.
- If you remove every registry, there is no default, and the marketplace shows only servers installed directly by URL.
There is no manual "Set as default" control.
Adding a registry
Call add_plugin_registry with a display name and the registry base URL. The platform requests {base_url}/v0.1/servers, so provide the host root without that path suffix.
https://registry.modelcontextprotocol.io
https://registry.example.comRead the result through list_plugin_registries and browse the catalog. A registry must answer before Oxagen can list its entries.
Removing a registry
Call remove_plugin_registry for the registry in this workspace. Its catalog entries disappear from discovery. Servers already installed from that registry stay installed.
If other registries remain, the most recently added registry becomes the default.
Role requirements
| Action | Required role |
|---|---|
| View registries | Workspace Member, Owner, or Viewer, or Org Owner/Admin |
| Add a registry | Workspace Owner or Org Owner/Admin |
| Remove a registry | Workspace Owner or Org Owner/Admin |
The default roles do not let a Workspace Admin view registries.