Manage your MCP servers
Describe the MCP servers your gateway reaches, check their tools and activity, and see what a server changed
MCP servers give agents something to do: without one connected, there are no tools to call, allow, or deny. Once you've added them, Inventory › MCP Servers & Tools is your registry of them, where you describe each one, check its tools, and see what changed. To add a server, see MCP Onboarding: from the catalog, as a custom server, or by approving a user's request.

Change a server after you add it
Catalog installs have no Edit button. Apart from its description and rotating BYO credentials, changing one means deleting it and adding it again. A custom server can be edited on its detail page.
Describe a resource
Two resources from the same provider look alike on the Connections page and in an agent's tool list.
A description tells users and agents which one is which, for example Acme's Jira and Confluence (acme.atlassian.net).
Add one to any resource. Use the Description field when you add it, or choose Edit on the resource later. For a catalog resource, the field starts with the catalog's description. A description is one line of plain text, up to 500 characters.
- Users see it under the title on the resource's detail page. They also see it under the resource's name on the Connections page, which lists the resources they sign in to with their own account.
- Agents read it next to the resource's tool prefix in the gateway's instructions.
The prefix is the slug followed by an underscore (
slack_), withx_in front for a custom server (x_acme_). In search mode,search_toolsresults include it once for each server that appears in them. - Catalog installs show your description in the gateway's instructions in place of the catalog's generic one. Leave the field as the catalog text, or restore that text, and the resource keeps following the catalog.
Resource details
Click any resource in the list to see its detail page:

- Available tools – every tool the MCP server exposes, with descriptions. For a resource that fans out to several upstream servers (Microsoft 365's Mail, Calendar, Teams, and so on), tools are grouped by upstream, collapsed by default
- Description – your description, shown under the title when you set one
- MCP Info – server URL, origin (catalog or custom), and, for custom servers, the authentication option
- Settings – for OAuth resources, how users authorize and which OAuth clients the gateway uses, including rotating a bring-your-own client ID and secret (details)
- Recent activity – audit events related to this resource
See what a server changed in a tool
A changed tool shows Changed on the Overview tab, and you can compare it with every earlier version. See Rug pull: tool change review.
Next steps
- Policies – write rules that decide which agents can use these tools.
- Credential modes – how the gateway authenticates to catalog resources.
- Add MCP server – the guided walkthrough.

