Tool catalog
Settings → MCP Registry is the organization’s view of everything agents could reach: the hosted catalog, your custom servers, and the enablement and setup state of each. This page is how to read it.
The registry at a glance
The registry is a searchable card grid — search matches server names, capabilities, credentials, and setup notes — with filter chips for the states that need attention: All, Enabled, Needs setup, Discovery failed, Public, and Custom.
Card badges tell the state without opening the panel:
| Badge | Meaning |
|---|---|
| Enabled / Disabled | Whether the organization has switched the server on. |
| Needs setup | Something is required before members can connect — the panel says what. |
| Discovery failed | The server’s OAuth metadata couldn’t be read; connections will fail until it’s resolved. |
| Public | No credential needed — the server serves public data. |
| Custom credentials | The server authenticates with admin-supplied headers. |
| Org server | A custom server your organization added, not a catalog entry. |
The detail panel
Configure opens the server’s panel: the enable toggle, an Authentication summary (personal connection, organization credential, or both — see Data scoping), OAuth discovery results and client configuration where relevant, and hand-written setup notes for servers that need preparation in the upstream service — required roles, app registrations, and a link to the vendor’s own documentation.
Tools, and keeping them current
A server’s tools are what policies decide over and what agents actually call. The panel shows when the tool list was last fetched; Refresh re-reads it from the server. Three moments to refresh deliberately:
- after enabling a server for the first time,
- after the upstream service announces new capabilities,
- when a plan reports a tool as unavailable that the vendor says exists.
Every refresh is an audit event, so “when did this server’s tool set change” has an answer in the audit log.
New tools arrive with no policy decision, which means unavailable — unless a policy has Include all future tools checked for that server, in which case they arrive pre-decided. Re-visit the policy after refreshing a server that grew new capabilities.