Manage entries
Entries are the individual MCP server definitions that appear in the catalog.
This guide covers how to publish new entries, edit them, and delete them through
the Cloud UI. You need the manageEntries role.
Only entries in a managed source can be edited from the Cloud UI. Entries that the Registry Server syncs from a git, API, or Kubernetes source are read-only here. Change those at their upstream source instead.
Publish a new entry
- Open the MCP Servers catalog and select the registry you want to publish to.
- Click Create to open the Create server dialog.
- Fill in the entry details:
- Name - the server's unique name in reverse-DNS form, for example
com.example/my-server. - Description - a short description of what the server does.
- Version - the entry's semantic version, for example
1.0.0.
- Name - the server's unique name in reverse-DNS form, for example
- Choose the Server source. This mirrors how you configure a server in
Stacklok Desktop:
- Local - a packaged server that Stacklok Desktop runs locally. Choose
the package Type (
oci,npm,pypi,nuget, ormcpb), the Transport (stdio,sse, orstreamable-http), the Image or package reference, an optional Port, and optional command arguments. - Remote - a server reachable over the network. Choose the Transport
(
streamable-httporsse) and enter the Remote URL.
- Local - a packaged server that Stacklok Desktop runs locally. Choose
the package Type (
- Set the Claims that control which users can see this server. Claims are required on an entry, and must be a subset of your own claims.
- Optionally configure how the server is run:
- Environment variables - add variables the server needs. Each can be Optional, Required, or Fixed (Uncustomizable), which locks the value so it can't be changed at install time.
- Secrets - add secret variables such as API keys, and mark each as required if needed.
- Custom metadata - add arbitrary
name=valuepairs to attach to the entry.
- Click Create server to publish the entry.
The entry appears in the catalog immediately, visible to users whose JWT claims match the entry's claims.
Edit an entry
- Open the entry's detail page.
- Click Edit to reopen the entry form.
- Update any field, including the server source, environment variables, secrets, claims, or custom metadata.
- Click Save to apply the changes.
Entries synced from a git, API, or Kubernetes source are read-only in the Cloud UI. The Edit and Delete buttons appear only for entries in a managed source.
Delete an entry
- Open the entry's detail page.
- Click Delete.
- Confirm the deletion in the dialog.
Deleted entries are removed from the catalog immediately. This action can't be undone.
Manage versions
An entry can have multiple versions. The catalog shows the latest version by default, and users switch between versions with the version selector on the detail page. Publishing a new version of an existing entry updates the catalog to show the latest version.
Next steps
- Browse the catalog to see how entries appear to users
- Manage sources to control where entries come from
- Manage registries to organize entries into registries
- Publish servers to the Registry Server for the entry format and the underlying admin API