Manage Integrations

An Integration is a remote MCP server the agent can work with. A Tenant Integration is one you register for everyone in your Tenant. This page covers what you can do in the Admin App today: register a server, with or without a sign-in, see the list, and rename.

You need the Right “Manage Integrations” to open the page. Admins hold it. Without it, Integrations is missing from the navigation of the Admin App.

Register an Integration

1. In the Admin App, open Integrations and select Register an Integration.
2. Enter the server’s address and select Check address. Before anything is registered, we ask the server, without signing in, whether it answers as an MCP server.
3. If it does, enter a name that your users will see, and optionally a description. Then select Register.

If the check fails, the dialog says why, in plain words:

• The address must start with https://. Plain http:// addresses are not accepted.
• The address points to a private or internal network. Only servers on the public internet can be registered. We check where the address leads, also after any redirect.
• Nothing answers at this address. Check for typos, and that the server is switched on and reachable from the internet.
• Something answers, but not as an MCP server. Check that you copied the server’s MCP address, and that its MCP server is enabled.

A server with a sign-in (OAuth)

If the server asks for a sign-in (OAuth), the check says so and you register it as an Integration with a sign-in. Every user of your Tenant then signs in to the server with their own account, on the Integrations page of their account menu, and the agent acts as them. Nobody gets more access than their own account has. Users don’t send you their credentials, and you can’t see them. You don’t register a client at the server yourself: the platform does that for your Tenant.

The Audit Log records when a user connects or disconnects an Integration, never a token.

A server with a personal API key

If the server takes a personal API key, select Each user enters a personal API key in the register dialog and name the header the key is sent in. The default is Authorization, where the agent sends Bearer and the key; any other header gets the key alone. The address check can’t tell such a server from a web page, because it refuses requests without a key, so the dialog accepts it once you say so and the address is reachable. Every user then enters their own key on their Integrations page, and you can’t see it. The Audit Log records when users save or delete a key, never the key.

No sign-in means the same access for everyone

If the server needs no sign-in, every user of your Tenant gets the same tools with the same access. The dialog says so before you register. Register such a server only if that is what you want.

What you see in the list

Each Integration shows its name, description, the server’s host, how it was added and when. The address and the kind of sign-in can’t be changed after registering: to use another address, register a new Integration.

Select the pencil next to an Integration to rename it or change its description.

Limit

A Tenant can have 50 Tenant Integrations. The page shows how many you use, and Register an Integration is off once you reach the limit.

The Audit Log

Registering and renaming an Integration leave entries in the Audit Log. They name the Integration by its ID and the server by its host, never more.

Deactivate an Integration

Select the power icon next to an Integration to deactivate it. The dialog says what happens before you confirm:

• The Integration disappears for every user of your Tenant at once. It leaves the list, the Integrations of new Conversations and every Conversation’s tools.
• Every user’s connection to it is deleted. Tokens are revoked at the server where it allows that, and deleted on our side either way.
• Conversations that had it selected stay readable. From their next message, a notice above the agent’s answer names the Integration as no longer available, and the agent tells the user.
• An Approval that waited for one of its tools can’t run any more. The agent tells the user why.

Deactivating can’t be undone. To use the server again, register it as a new Integration. Every user then connects again. The Audit Log records “Deactivated an Integration”.

Activate an Integration from the Catalog

Below the list, the Integration Catalog offers Integrations we know, such as Metabase, which you activate by entering the address of your own instance. See Connect Metabase.