Claude Metabase Community connectorWhat this community server lets Claude do in your Metabase.
The Claude Metabase Community connector exposes 6 tools. 5 read your Metabase instance, 1 clears the connector's own cache. It is a community extension, separate from the Metabase connector: here is what it reads, what it exports, and what it blocks out of the box.
Verified Trustpilot reviews · AI, automation & growth agency
What it changes for an analyst who lives in Metabase
This is not Metabase's own connector. An independent developer, Jericho Sequitin, publishes it, and it installs on your machine through Claude Desktop. It plugs Claude into your instance so it can find saved questions and dashboards, run queries and pull large files.
Find the right saved question. search runs across every item in the instance, and retrieve returns details for several cards or tables in one call, up to 50 IDs at once.
Answer a number someone asks for mid-meeting. execute runs a SQL query or a saved card, returning 100 rows by default and never more than 500.
Hand a big dataset to the colleague who lives in spreadsheets. export pulls up to a million rows as CSV, JSON or XLSX into your local export folder.
What Claude will not do as shipped: change your database. Read-only mode is on by default and restricts execute to SELECT statements; the publisher documents it as a setting you can switch off, which is why the query tool counts as a read only while that mode stays on. It does not create questions or dashboards either, since no tool on the sheet does that. Nothing runs on a schedule. For recurring reports you want an automation tool, a different job, and the Integrations hub covers it.
The vocabulary in one minute
Five terms to know before you install this community server.
- Connector
- A one-time link between Claude and a service you already use, which lets Claude work there while it replies to you.
- Tool
- One named capability the connector opens to Claude. Claude picks what it needs by itself; the directory sheet lists them all.
- Authorization
- The step where you give Claude access to your Metabase, here through an API key or credentials. Granted once, per person.
- Approval
- The confirmation Claude waits for in the chat before carrying out something that changes anything on your side.
- MCP
- The shared standard behind connectors; it is what lets an assistant like Claude talk to an outside service.
Connect Metabase Community to Claude in three steps
- 01
Find it in Claude Desktop
In Claude Desktop, open Customize, then Connectors, and look for Metabase Community. In a Team or Enterprise organisation, it first has to be switched on by an Owner or Primary Owner.
- 02
Start the connection
Start the installation from its row. The extension then asks for access to your Metabase instance; the publisher's README lists an API key or an email and password. The exact screens depend on Claude Desktop, so follow what it shows. If the link breaks later, use Disconnect and connect again.
- 03
Check the access you hand over
Check what you hand over before confirming: the key or account you enter, not Claude, decides what the connector can reach in Metabase. Read-only mode is on by default; leave it that way unless you mean to allow SQL writes.
All 6 tools, grouped by what they do
Metabase Community gives Claude 6 tools: 5 that read your account, 1 that change something in it.
Two groups: what Claude reads in Metabase, and the one tool that changes something, on the connector's side. Tool names stay as Claude shows them.
- 5 read
- 1 write
What Claude reads (5)
5 toolsFive tools that consult your instance, SELECT queries included in the default mode.
search
Runs Metabase's native search API across every item in your instance, so a saved question, a dashboard or a table can be located without knowing where it is filed.
list
Returns every record of a given type, whether cards, dashboards, tables, databases or collections, with responses trimmed to the essential fields only.
retrieve
Fetches details for specific items by their ID, processing requests concurrently, with up to 50 IDs handled in a single call to the tool.
execute
Runs a SQL query or a saved card and returns the result, 100 rows by default and 500 at most. In read-only mode, which is on by default, only SELECT statements go through.
export
Pulls large datasets, up to a million rows, out as CSV, JSON or XLSX into the export folder configured on your machine. Your Metabase data stays as it was.
What Claude changes (1)
1 toolOne tool acting on the connector's cache, not on your data. No dedicated confirmation is described.
clear_cache
Approval: see the ruleEmpties the connector's internal cache, with what the publisher calls granular control. Metabase data is untouched; only the copy the connector keeps for itself is cleared.
What needs your go-ahead
Claude's default is to stop and wait for your yes before any action it carries out in your name. That request shows up in the conversation at the moment of the action.
Here no source describes a confirmation tied to a specific tool, so the default rule covers clearing the cache. The real safeguard sits elsewhere, in the server's read-only mode, which stays on until you switch it off. On Team and Enterprise workspaces, owners decide whether members may let actions through without a prompt, and they can cap a connector for the whole organisation. Claude never has more access than the key or Metabase account you hand it.
Which plans it's available on
None of the 819 sheets in the official directory shows plan availability. Connector by connector, that information is not published anywhere.
The general rule is sourced: desktop extensions such as this one install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. In a Team or Enterprise organisation, members can only use a connector once an Owner or Primary Owner has switched it on. For the current status, the connector's sheet in the official directory is the reference.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: no export goes out overnight, and no alert watches your metrics.
This server is community-built: its publisher is an independent developer, not Metabase, and only its README documents it, with no page in Claude's help centre. The directory badge is not a security audit, and a connected community connector has exactly the same access as any other. Anthropic does not guarantee its tools behave as described, so connect it only if you know who publishes it. Its README is dated July 2026 and documents version 1.1.7 of the package.
Need help connecting Metabase Community to Claude?
A person reads every message.
