Skip to main content
The catalog ships with a curated set of servers. To use one of your own — an internal service, or a commercial MCP endpoint you subscribe to — register it as an endpoint.
1

Register the endpoint

For an HTTP-transport server:
For a server you run as a local process:
Choose the scope deliberately: personal for yourself, workspace for your team, org for everyone in the organization.The server derives a qualified name from the name you gave it, of the form endpoint/<workspace_id>/<slug>. That’s what the remaining commands take.
Registration succeeds even if the server can’t be reached or authenticated yet. It registers with an empty tool list, and introspection fills that in once it can connect.
2

Attach a key

Most real servers need authentication:
If the server expects the key somewhere other than a bearer token:
connect-key introspects automatically after attaching, so a successful call also tells you the server’s tools.This is an idempotent upsert — run it again to rotate the key.
3

Confirm the tools

An empty tool list after a successful key attach usually means the key lacks permission for the tools you expect, rather than that the server has none.
4

Confirm it wins resolution

If a name collides across tiers, the most specific wins. This shows you which entry an agent will actually get, and what it beat.

​
Using it in an agent

Once the server has tools, reference it when planning:
Then check the agent can actually reach it:

​
Rotating and removing

disconnect-key is idempotent and reports removed=false when there was nothing to remove.

​
See also