Browsing the catalog
Registering your own server
mcp add-endpoint
Register an MCP server you host or subscribe to. The server derives a qualified name of the form endpoint/<workspace_id>/<slug-of-name>.
stdio server:
Registering succeeds even if the server can’t be reached yet — it registers with an empty tool list, and introspection fills it in once it can authenticate. Registering a duplicate name without
--update is rejected.
mcp connect-key
Attach a bring-your-own API key to a registered endpoint, then introspect it automatically.
This is an idempotent upsert — running it again replaces the key.
mcp introspect
Re-list a registered server’s tools.
mcp disconnect-key
Remove the stored key from an endpoint server.
removed=false when there was nothing to remove.
mcp remove-endpoint
Delete an endpoint server.
Repositories
Sync a GitHub repository of MCP servers into the catalog.mcp repo add
Adding auto-imports the repository’s servers unless you pass
--no-sync.
Only GitHub URLs are accepted. Private repositories work using your own connected GitHub credential — see Importing private GitHub repositories.
The rest of the repo commands
repo scope takes the same --scope and repeatable --workspace options as repo add.
When a sync needs a credential
A private repository sync with no usable GitHub credential returns a typed error:--json this prints as pure JSON on stdout so a script can branch on it. See Credential problems.
See also
- Skills and MCP servers — the model.
- Add your own MCP server — walkthrough.
jstm registry— which entry wins when names collide.