# Metabase MCP connector

The Metabase connector brings your questions, dashboards, collections and users into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so anyone can ask for a query or a dashboard in plain language inside their own Metabase access.

Source: https://elaichi.ai/connectors/metabase/

## Facts

| | |
| --- | --- |
| Application | Metabase |
| Category | Analytics |
| AI tools | 458 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Metabase is connected

- Build a dashboard of closed deals by rep this quarter
- Which Metabase dashboards did people open most last month?
- Add a card for refunds by week to the finance dashboard

## Connect Metabase in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Metabase.
2. Optionally set Share with, then press Connect.
3. Paste a Metabase API key. One person generates a token in Metabase and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Metabase tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Metabase MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Metabase MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Metabase MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Metabase MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Metabase MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Metabase to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Metabase tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Metabase through Elaichi

### Build a pipeline dashboard from a plain question

Sales. Describe the numbers you want, such as closed deals by rep this quarter, and the agent writes the Metabase query and saves it to a dashboard your team can open on Monday.

### Refresh the month-end dashboard without a ticket

Finance. Ask for a new card on the revenue dashboard and the agent updates it in Metabase, so you stop queuing behind the data team for every small change.

### See what the company actually looks at

Operations. Pull the most popular dashboards and recently viewed items in Metabase to find out which reports matter and which ones nobody has opened in months.

### Answer a volume question before the standup

Support. Type "tickets by channel this week" and get a Metabase query built and answered, with the result ready to paste into the standup notes.

### Keep the Metabase workspace tidy

Data. Create collections for each team, place new questions and dashboards into them, and hand off a clean structure rather than a pile of untitled questions.

### Onboard and offboard Metabase users in a sentence

IT. Add a new hire, update someone's name or email after a change, or remove a leaver's Metabase account, all from the same chat you use for everything else.

## Elaichi vs Zapier MCP vs Composio for Metabase

All three can connect Metabase to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Metabase tools | Allow or restrict single Metabase tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Metabase call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Metabase to Claude?

Connect Metabase in Elaichi by pasting a Metabase API key, which you create in your Metabase admin settings; there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your Metabase questions, dashboards and collections.

### Does Metabase work with ChatGPT and Cursor as well as Claude?

Yes. Once Metabase is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Metabase once and every client you use picks it up.

### What can an AI agent actually do with my Metabase data?

It can turn a plain question into a Metabase query, build or update a dashboard, create a collection to keep things organized, run a saved action, and tell you which dashboards people open most. It can also add, update or remove Metabase users. Short, concrete asks such as "orders by region last month" work better than long sentences.

### Does connecting Metabase give the AI access to every collection and dashboard?

No. The agent works inside the Metabase access of the person who signed in, so a dashboard or collection they cannot open in Metabase stays out of reach for them in Claude too. Elaichi can narrow that access further with restrictions, and it never widens it.

### Can my team share one Metabase connection?

Yes. One person connects Metabase in Elaichi and shares the connection with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every Metabase query or dashboard change.

### Can I stop an agent from deleting or changing things in Metabase?

Yes. Restrictions in Elaichi apply per action, such as deleting a Metabase user or updating a dashboard, and are set on a role or on one person. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Metabase connection when someone leaves?

Offboarding them in Elaichi ends their access to Metabase through every client at once. A Metabase connection shared with the team keeps working for everyone else. If you want to remove Metabase entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client.

### Does the Metabase MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Metabase is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Metabase?

Yes. Both let Claude, ChatGPT or Cursor use Metabase. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Metabase call.

### How is Elaichi different from Composio for Metabase?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Metabase: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 458 Metabase tools

Every tool below is callable through https://api.elaichi.ai/mcp once Metabase is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Metabase session** (Create). Create a login session in Metabase by authenticating a user. Returns an empty 204 response on success. Required: username, password.
- **List all Metabase users** (List). List Metabase users. Returns: id, email, first_name, last_name. Active users are returned by default.
- **Get single Metabase user by ID** (Get). Get a Metabase user by id. Returns: id, email, first_name, last_name. Required: id.
- **Delete a Metabase user by ID** (Delete). Disable a Metabase user account by id (the account is disabled, not permanently removed). Returns an empty 204 response on success. Required: id.
- **Create a Metabase user** (Create). Create a new Metabase user by email address. Returns the created user record including id, email, first_name, and last_name. Required: email. Fails with a 400 error if the email address is already taken.
- **Update a Metabase user by ID** (Update). Update an existing Metabase user by id, including profile fields, locale, and group memberships. Returns the updated user record including id, email, first_name, and last_name. Required: id. Only personal users can be updated this way; API-key users return 404.
- **Metabase users current** (Action). Get the current Metabase user — the account the connected API credential belongs to. Returns: id.
- **List all Metabase action publics** (List). List Metabase actions that have public UUIDs and are publicly accessible when public sharing is enabled. Returns: id, created_at, updated_at.
- **Create a Metabase action** (Create). Create a new Metabase action. Returns the created action object (per the upstream action schema; includes the action id). Required: name, type, model_id.
- **Delete a Metabase action by ID** (Delete). Delete a Metabase action by id. Returns an empty 204 response on success. Required: id.
- **Metabase actions execute** (Execute). Execute a Metabase action by id; the parameters field carries mapped dashboard parameter values. Returns an empty 204 response on success. Required: action_id.
- **Get single Metabase action by ID** (Get). Get a single Metabase action by id. Returns the action object (per the upstream action schema; includes the action id). Required: id.
- **List all Metabase actions** (List). List Metabase actions that can be used for QueryActions; by default all viewable actions are returned. Returns an array of action objects (per-item fields follow the upstream action schema; id is the action identifier). Optional: model_id to limit to actions on a particular model.
- **Update a Metabase action by ID** (Update). Update an Action in Metabase by id. Returns the updated Action on success. Required: id.
- **List all Metabase activity most recently viewed dashboards** (List). Get the most recently viewed dashboard for the current user in Metabase. Returns an empty 204 response when the user has not viewed any dashboards in the last 24 hours.
- **List all Metabase activity popular items** (List). List the most popular things on a Metabase instance. Returns up to 5 popular items, each with an id and type-specific attributes.
- **List all Metabase activity recent views** (List). List the cards, models, tables, dashboards, and collections the current user has viewed most recently in Metabase. Returns up to 100 items with their id and model-specific attributes, capped at 20 per model type. Deprecated upstream.
- **Create a Metabase activity recent** (Create). Add a model to the current Metabase user's list of recently selected items. Returns an empty 204 response on success. Required: context, model, model_id.
- **List all Metabase activity recents** (List). List the recent items the current Metabase user has been viewing or selecting most recently. Returns the recents list of recent items. Required: context.
- **Create a Metabase agent collection** (Create). Create a new Collection in Metabase via the Agent API, either at the root level or nested under a parent collection. Returns: revision, groups. Required: name.
- **Create a Metabase agent construct native query** (Create). Construct a native (raw SQL) query against a database in Metabase. Wraps the supplied SQL into a serialized native query and returns it base64-encoded as query, ready to save as a question; the SQL itself is not executed (MBQL execution endpoints reject native queries). Required: database_id, sql.
- **Create a Metabase agent construct query** (Create). Construct an MBQL query in Metabase from a portable MBQL 5 external-query JSON payload. Returns the base64-encoded MBQL query in the query field, ready to execute via /api/agent/v1/execute or paginate via /api/agent/v2/query. Required: query.
- **Create a Metabase agent dashboard** (Create). Create a Metabase dashboard, optionally populated with existing saved questions passed as question_ids; cards are positioned automatically on the grid by display type. Returns: id, collection_path. Omitting collection_id saves to your personal collection; pass an explicit null for the root collection. Required: name.
- **Update a Metabase agent dashboard by ID** (Update). Update a Metabase dashboard by id with patch semantics — only fields you pass are changed. Returns: id, collection_path. Required: id. Archiving is a soft delete (there is no delete endpoint); reverse it with archived: false. Dashcard edits go under dashcards as ordered action entries.
- **Create a Metabase agent execute SQL** (Create). Execute a raw SQL query against a Metabase database. Returns the query result with data (column metadata in cols plus result rows), row_count, status, and running_time. Required: database_id, sql.
- **Create a Metabase agent execute** (Create). Execute an MBQL query in Metabase. Returns: data, row_count, status, running_time, error. Limits: 2000 rows for simple queries, 10000 for aggregated. Required: query.
- **Create a Metabase agent metric** (Create). Save a previously constructed query as a named metric in Metabase; the underlying query must have exactly one aggregation and at most one date/datetime grouping. Returns: id, name, description, display, collection_id, collection_path, archived. Required: query, name.
- **Update a Metabase agent metric by ID** (Update). Update a saved Metabase metric with patch semantics - only the fields you pass are changed. Archiving (archived: true) is a soft delete; there is no delete endpoint. Returns: id, name, description, display, collection_id, collection_path, archived. Required: id.
- **List all Metabase agent pings** (List). Ping the Metabase Agent API health check endpoint to verify connectivity. Returns: message. Takes no parameters.
- **Create a Metabase agent query** (Create). Execute a portable MBQL 5 representations JSON query in Metabase and stream the results with continuation-token pagination. Returns: results, column_metadata, continuation_token. Accepts either a JSON body with the query or a continuation_token from a previous response to fetch the next page.
- **Create a Metabase agent question** (Create). Save a previously constructed query as a named question (card) in Metabase. Returns: id, name, collection_path. Omitting collection_id saves the question to the caller's personal collection; pass an explicit null to save it to the root collection. Required: name, query.
- **Update a Metabase agent question by ID** (Update). Update a saved Metabase question (card) with patch semantics — only the fields you pass are changed. Returns: id, name, collection_path. Required: id. Use collection_id to move the card, archived true to archive it (soft delete, reversible with archived false), or query to replace the underlying query.
- **Create a Metabase agent read resource** (Create). Read one or more Metabase resources by resolving `metabase://` URI patterns, with per-URI validation and permission checks. Returns: resources, output. Up to 5 URIs per call. Required: uris.
- **Metabase agents search** (Search). Search Metabase for tables, models, metrics, saved questions, dashboards, and collections using term-based and/or semantic queries; results are ranked with Reciprocal Rank Fusion when both query types are provided. Returns: id, attributes.
- **Get single Metabase alert by ID** (Get). Get a single Metabase alert by id. Returns: id, archived, attributes. Required: id. Metabase plans to remove the /api/alert endpoints in a future version (transitioning to a new notifications architecture).
- **List all Metabase alerts** (List). List Metabase alerts the current user created or will receive, or all alerts if the user is an admin. Returns per alert: id, archived, and the remaining alert attributes object. Metabase plans to remove the /api/alert endpoints in a future version (transitioning to a new notifications architecture).
- **List all Metabase analytics anonymous stats** (List). Get the anonymous usage stats collected about this Metabase instance — the data it phones home. Meant for testing and admin introspection. Returns an opaque usage-stats payload with content-type-specific fields; no fixed shape is documented.
- **Create a Metabase analytics internal** (Create). Record a batch of internal Metabase frontend analytics events as Prometheus metrics; only documented frontend metric counters can be incremented and other events are ignored. Returns an empty 204 response on success. Required: events.
- **Create a Metabase analytics proxy** (Create). Forward a batch of Snowplow tp2 analytics events from the client to sp.metabase.com server-side through Metabase, bypassing the page's connect-src CSP. Returns an empty 204 response on success. Required: data, schema.
- **Create a Metabase API key** (Create). Create a new Metabase API key (and an associated user) with the provided name and permissions group. Returns: id, name, group_id. Required: name, group_id.
- **List all Metabase API keys** (List). List Metabase API keys with the default scope. Returns: id, name, group_id. Non-paginated; all keys are returned in one response.
- **Delete a Metabase API key by ID** (Delete). Delete a Metabase API key by id. Returns an empty 204 response on success. Required: id. Deleted keys cannot be recovered — a new key must be created.
- **Update a Metabase API key by ID** (Update). Update a Metabase API key by id, changing its group and/or its name. Returns the updated key's id, name, and group_id. Required: id.
- **Create a Metabase execute value** (Create). Fetch the values for filling in a Metabase action's execution parameters. Pass PK parameters and values to select; inputs go in the request body rather than the query string so their values stay out of URLs and logs. Returns a map of the fetched parameter values. Required: action_id, action-id, parameters.
- **Create a Metabase execute values execute** (Create). Fetch the values for filling in a Metabase dashcard's execution parameters, passing PK parameters and values to select. Returns a JSON object of parameter values whose keys depend on the dashcard. Required: dashboard_id, dashcard_id.
- **Metabase public links bulk delete** (Delete). Delete the publicly-accessible link of a Metabase card, revoking its public access. Returns an empty 204 response on success. Required: card_id.
- **Metabase public links bulk delete action** (Delete). Delete the publicly-accessible link of a Metabase action, revoking its public access. Returns an empty 204 response on success. Required: action_id.
- **Metabase public links bulk delete dashboard** (Delete). Delete the publicly-accessible link of a Metabase dashboard, revoking its public access. Returns an empty 204 response on success. Required: dashboard_id.
- **Metabase public links bulk delete document public link** (Delete). Delete the public link of a Metabase document, revoking public access so the existing link stops working. Returns an empty 204 response on success. Requires superuser and public sharing enabled; 404 if the document is missing, archived, or has no public link. Required: document_id.
- **Create a Metabase public link** (Create). Generate a publicly-accessible link for a Metabase card. Returns the UUID used to build the public link; if the card is already shared, the existing UUID is returned instead of a new one. Public sharing must be enabled. Required: card_id.
- ...and 408 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
