Connect Metabase

Metabase is the first entry of the Integration Catalog. Once you activate it, everyone in your Tenant can connect to your Metabase with their own Metabase account, and the agent works with it on their behalf. Nobody gets more access than their own Metabase account has.

You need the Right “Manage Integrations” to activate it. Admins hold it. Nothing in the Integration Catalog is available to users until you activate it.

Before you activate

• Turn on Metabase’s MCP server. It is off by default. A Metabase admin switches it on in Metabase’s admin settings. It needs a Metabase version that has an MCP server (version 0.60 or newer). Without it, the activation fails with “MCP is not enabled”.
• Make your Metabase reachable over the internet. The address has to start with https:// and lead to a server on the public internet. Addresses in a private or internal network are refused, also after a redirect.

Activate Metabase

1. In the Admin App, open Integrations. Below your list, the Integration Catalog shows Metabase with a link to this guide.
2. Select Activate Metabase.
3. Enter the address you open Metabase at, for example https://metabase.example.com. We add the rest of the address ourselves. Pasting the full MCP address that Metabase’s MCP settings show, such as https://metabase.example.com/api/metabase-mcp, works too. If Metabase runs under a path, such as https://example.com/metabase, enter it with that path.
4. Select Activate.

Before anything is activated, we ask your Metabase whether it answers as an MCP server and asks users to sign in. If it doesn’t, the dialog says why, in plain words:

• The address must start with https://. Plain http:// is not accepted.
• The address points to a private or internal network. Only Metabase instances on the public internet can be activated.
• Nothing answers at this address. Check for typos, and that Metabase is switched on and reachable from the internet.
• MCP is not enabled. Metabase answers, but not as an MCP server. Ask a Metabase admin to turn on its MCP server, and check the address.

Metabase then appears in your list of Tenant Integrations, marked as activated from the Catalog. You can rename it, and you can activate it again for another instance, such as a test Metabase. A Tenant can have 50 Tenant Integrations in all.

What your users see

Metabase appears on the Integrations page in the account menu of every user, and in the selection of a new Conversation. A user selects Connect, signs in at your Metabase’s own sign-in page and allows the access. You don’t create an OAuth client in Metabase: we register ours at your Metabase for you.

The agent then uses Metabase’s tools as that user. Tools that only read, such as running a saved question, run without asking. Tools that change something or run SQL ask for an Approval first.

The Audit Log records the activation, with the Integration, the host of your Metabase and the version of the Catalog entry, never a token. More on registering other servers and on the sign-in is in Manage Integrations.