Skip to main content

Manage sources

Sources define where MCP server entries come from. A registry is made up of one or more sources. This guide covers how to manage sources through the Cloud UI. You need the manageSources role.

For the full definition of each source type and the options that aren't yet editable in the UI, see Registry Server configuration.

View sources​

Open Registries in the navigation bar, then select Sources in the sidebar. The list shows each source's name and type. Use the search box to filter by name or type.

Source types​

When you create a source, choose one of four types:

  • Git - syncs entries from a registry file in a git repository.
  • API - syncs entries from an upstream Registry Server that implements the registry API.
  • Kubernetes - auto-publishes entries from annotated, operator-managed resources in a cluster namespace.
  • Managed - holds entries created directly through the Cloud UI or the Registry Server API. This is the source type you publish to when you manage entries.

Create a source​

  1. With the Sources list open, click Add a source.
  2. Enter a Name for the source.
  3. Choose the Type and fill in its configuration:
    • Git - the Repository URL, the Branch to sync from, and a Sync interval (for example 1h, 30m, or 5m).
    • API - the API Endpoint and a Sync interval.
    • Kubernetes - the Namespace to watch.
    • Managed - no additional configuration.
  4. Add the Claims that control which users can see the source's entries. Claims are required on a source.
  5. Click Save.

The Registry Server begins syncing entries from the new source. Entries appear in the catalog once the initial sync completes.

Configured through the API or config file

Some source options aren't available in the Cloud UI yet:

  • Git sources sync from a branch. To pin a tag or commit, or to authenticate to a private repository, configure the source through the Registry Server API or configuration file.
  • Sync filters that control which entries a source imports must also be set through the API or configuration file.

Source and registry claims​

Claims attach to both sources and registries, and they compose. Claims are required on a source but optional on a registry. A common pattern is to apply a broad claim at the registry layer and finer-grained claims at the source layer, so a single registry can present different contents to different roles.

Edit a source​

  1. Open the source's actions menu and select Edit source.
  2. Update the configuration. The source name can't be changed.
  3. Click Save to apply the changes.
note

Config-managed sources are read-only. Their actions menu shows View source instead of Edit source.

Delete a source​

  1. Open the source's actions menu and select Delete source.
  2. Confirm the deletion in the dialog.

Deleting a source removes the entries that originated from it. Config-managed sources can't be deleted from the Cloud UI.

View source entries​

Select View entries from a source's actions menu to see every entry the source provides, before any registry-level filtering or deduplication is applied.

Next steps​