Skip to main content

Tools and connectors in the Catalog

The Catalog's Tools and Connectors sections show what agents can be given: MCP servers, which give an agent tools to call, and connectors, which bring an outside system's content into Knowledge. Neither section stores or deploys anything. Each reads the list the Control Room holds and hands the action to the Control Room page that owns it.

Who can use it: the Member role reads both sections. Deploy and Connect need Control Room access: the Admin role or any of the seven grants. Whether a server is running is shown to the Builder role and above.

Tools​

The page describes MCP servers as giving an agent tools to call, and says a server has to be deployed in your organisation before an agent can use it. The list is the server catalog the Control Room's Tools page holds, under Server catalog.

  1. Find a server

    Search by name or what a server does, or pick a category. The line above the cards counts the servers, or how many of them match.

  2. Read its status

    Each card and each server's page says where the server stands in your organisation: Running here, Starting here, Deployed here, stopped, Deployed here, not working or Not running here. Below the Builder role the card reads Status is shown to builders and admins.

  3. Open the server

    Select a card. The page shows the server's category, its status, What it does and Tools it declares. A server that is not running adds that no agent can call it yet. When the catalog does not list a server's tools, the page says they are discovered when it is deployed.

  4. Deploy it, or manage it

    Deploy opens the Control Room's deploy flow on that server: see Add an MCP server. A server already deployed offers Manage in Control Room instead. Without Control Room access, the place of Deploy holds Ask an admin, and a deployed server offers nothing more.

MessageWhat it means
The servers did not loadThe list could not be read. Nothing is wrong with your servers; select Try again
No servers on offer yetThis installation's server catalog is empty. An administrator refreshes it in the Control Room
Status could not be readWhich servers run here could not be read; the list itself is fine
Server not foundA link names a server the catalog no longer holds; Browse all servers returns to the list

Connectors​

The page says a connector brings an outside system's content into Knowledge, where agents can search it, and does nothing until a source is connected with it. The list is exactly the one Connect Source offers in the Control Room's Knowledge, in the same categories, such as Knowledge Base, Cloud Storage, Ticketing, Messaging and Sales.

  1. Find a connector

    Search by name or what it brings in, or pick a category.

  2. Read its status

    A card reads Connected with how many sources of that kind your organisation has, or Not connected. The count is of the knowledge sources you can open: a source shared only with another team is not counted here.

  3. Open the connector

    Select a card. What it brings in describes the connector as the wizard does and says how it signs in: with OAuth, with an API key or token, or with no sign-in at all. A connector that carries the source's own permissions says so: people find only what they may open in the source system. Sources in this organisation names the sources of this kind you can open.

  4. Connect it

    Connect opens Connect Source in Knowledge with this connector already chosen; the setup itself is on Connect sources. Without Control Room access, Ask an admin stands in its place, unless a source of this kind already exists that you can open.

Ask an admin​

Ask an admin names your organisation's administrators, with the reason the action needs one: only an admin can deploy a server, or connect a source from here. When no administrator is set, it says so. It is a message, not a request: nothing is sent to anyone, so contact one of the people it names yourself.

Describes the platform as of .

Was this page helpful?