Claude Metabase connectorWhat Claude can do in your Metabase.
The Claude Metabase connector exposes 11 tools. 7 search tables and metrics, read field values, build and run queries or draw a chart, 2 save questions and dashboards, and 2 stay undocumented. First step: a Metabase admin has to switch the feature on.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug Metabase into Claude
Metabase already knows your tables, your metrics and who may see what. With the connector, Claude asks it directly: you type "what was our Q3 revenue?", Claude finds the right table or metric, builds the query, runs it and answers with your figures, or with a chart when you ask it to show them. It all runs within the permissions of the person who connected.
A number without opening the query builder. search finds the table or metric, construct_query prepares the query and execute_query returns the result with its columns, row count and execution time, so you can see where the figure comes from before you quote it.
A chart inside the conversation. Ask Claude to show or visualize the data and visualize_query renders an inline bar, line or table chart you can switch between.
A finding kept for the team. create_question saves a query as a named question, and create_dashboard starts a new dashboard, optionally filled with saved questions.
What it does not do: it cannot turn itself on, since an admin controls it; it caps results at 2,000 rows; and its sheet carries no tool that edits or archives existing content. It never runs on a schedule either. For recurring exports or alerts, the Metabase n8n integration and the Metabase Make integration run without anyone in the chat.
Five words before you connect
The vocabulary of Claude connectors, explained once.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector hands to Claude. Claude decides which ones to call while it answers, and the directory sheet lists them all.
- Authorization
- Metabase's own consent page, where you approve the connection with your Metabase login. It is granted per person and can be revoked.
- Approval
- The confirmation Claude waits for before a change to your account, shown in the conversation at the moment it matters.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Metabase.
Connect the Claude Metabase connector in three steps
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and find Metabase. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization before anyone can connect.
- 02
Point it at your Metabase
Click Connect. Metabase asks for the address of your own instance, then opens its consent page, where you log in to your Metabase if you are not already and approve the connection.
- 03
Approve with care
That consent page belongs to Metabase, not Claude, and the access it grants follows your Metabase permissions. Accept it; Disconnect removes the link, and an admin can see every approval in Metabase's logs.
The 11 tools of the Metabase connector
Metabase gives Claude 11 tools: 7 that read your account, 2 that change something in it, and 2 no official source describes.
Metabase's documentation describes most of these tools; the directory description covers two more. The last two carry a name and nothing else. Names stay as Claude shows them.
- 7 read
- 2 write
- 2 not documented
What Claude reads (7)
7 toolsSearch, field values, query building and running, and inline charts.
search
Finds tables and metrics by keyword or by a question in plain language. Claude uses it to locate the right source before it builds anything.
get_table_field_values
Explores the values a field of a table holds, which the directory description names as one of the connector's uses. Claude reads them to filter on the right spelling.
get_metric_field_values
Explores field values on the side of a metric, the counterpart of the table version. The directory description is the only text that covers it.
construct_query
Prepares a query against a table or a metric and returns a handle that the run tools accept. On its own it fetches no data.
execute_query
Runs a query built beforehand and returns the results with column details, row count and execution time.
query
Accepts a query handle, a fresh query or a continuation token, runs it and pages through large results.
visualize_query
Renders a query's results as a chart inside the conversation.
What Claude saves (2)
2 toolsNew questions and new dashboards. Metabase says some clients ask you to approve each tool the first time it is used.
create_question
Approval: see the ruleSaves a query as a named question in your Metabase, so the team can open it later like any other.
create_dashboard
Approval: see the ruleCreates a new dashboard, optionally filled with saved questions.
Named, not documented (2)
2 toolsThe directory lists these two names, but no official source says what they do, so this page does not guess.
get_table
No official source describes this tool: the directory lists its name, and Metabase's current documentation does not mention it. This page does not guess what it returns.
get_metric
Only the name of this tool is published. Neither the directory sheet nor Metabase's documentation explains it, so its behaviour stays undocumented here.
What Claude checks with you first
By default, Claude stops and asks before each action it carries out on an account for someone, right in the conversation.
Metabase adds a detail of its own: some clients, Claude Desktop among them, ask you to approve each tool the first time it is used, and you can approve or block tools in the client rather than in Metabase. On Team and Enterprise, workspace owners decide whether members may let some actions through without being asked, and can close writing for everyone. Above all, the access is scoped to the connecting person's Metabase permissions: Claude cannot see data you cannot see.
Which Claude plans it runs on
None of the 819 directory sheets states availability by plan, and no official source publishes it connector by connector.
The published rule is general: remote connectors like this one are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization before members connect. For the current state of Metabase, open its sheet in the official directory. On the Metabase side, the feature also depends on your admin.
Limits of the Claude Metabase connector
A connector is not an automation: Claude calls these tools while it answers you, and nothing runs on a schedule or when a number moves.
This page relies on the directory sheet and on Metabase's documentation: neither Claude's help center nor Anthropic's developer docs cover this connector. The two sources also disagree on the tool list, since Metabase's current page names tools the sheet does not carry. The verification badge is not a security audit, and Anthropic states on every sheet that it does not control a publisher's tools. Other options sit in the Integrations hub.
Need help connecting Metabase to Claude?
A person reads every message.
