
This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.

The Metabase MCP server lets an AI app search your Metabase content, run queries and saved questions, and create or edit questions, dashboards, metrics and alerts. It is built into Metabase itself, so an admin switches it on and you point your client at your own Metabase URL.
Checked against: Metabase MCP server docs and MCP server tools reference (both for Metabase v0.65), plus the Claude connector listing, on 2 November 2026. eSEOspace did not install or test this server.
Key Takeaways
- The endpoint lives on your own instance:
https://{your-metabase-url}/api/metabase-mcp. - An admin turns it on at Admin > AI > MCP. It stays off if "Disable all AI features" is on.
- Sign-in uses OAuth 2.0 through Metabase's built-in OAuth server, and tokens never exceed the user's Metabase permissions.
- Five scopes split read, query, raw SQL, content writes and alerts, so you can grant less than full access.
- A separate "Metabase (Unofficial, Community)" connector by another developer is also in Claude's directory. This profile covers the official server by Metabase.
At a glance
| Item | Detail |
|---|---|
| Publisher | Metabase |
| Official? | Yes |
| Hosting | Built into your Metabase instance (self-hosted or Cloud) |
| Transport | HTTP (Claude Code uses --transport http) |
| Sign-in | OAuth 2.0 with dynamic client registration; JWT bearer for headless use on Pro and Enterprise |
| Read or write | Read and write, controlled by scopes |
| Price | No separate MCP price; per-group tool limits and MCP analytics are Pro and Enterprise features |
| Source code | Part of Metabase; the MCP docs do not link a separate repo |
| Status | Not stated |
What it can do
Metabase's tools reference lists 23 tools. Each runs as you and respects your Metabase permissions.
| Area | Tools | Access |
|---|---|---|
| Find and read | search, browse_collection, browse_data, get_content, get_parameter_values, glossary, learn | Read |
| Run queries | execute_query, run_saved_question, visualize_query, render_drill_through | Read-only |
| Raw SQL | execute_sql | Write-capable |
| Build content | question_write, dashboard_write, metric_write, measure_write, segment_write, document_write, collection_write, duplicate_content, bookmark_content | Write |
| Deliveries | alert_write, subscription_write | Write |
execute_query runs structured queries with no raw SQL, and it can validate a query without running it. visualize_query and render_drill_through draw inline charts, but only in clients that support inline visuals. Metabase lets you switch between bar, line and table charts when the data fits.
The Claude directory listing shows an older set of 11 tool names, such as construct_query and create_dashboard. The v0.65 tools reference is the current list.
How to connect it
First, an admin opens Admin > AI, selects the MCP tab and turns on the MCP server toggle. You do not need an AI provider configured in Metabase, because the client supplies the model. The admin can copy the server URL from the MCP settings page.
For Claude Code, Metabase's docs give this command:
claude mcp add --scope user --transport http metabase https://{your-metabase-url}/api/metabase-mcp
Drop --scope user to limit it to the current project. Then run /mcp, select Metabase and click Authenticate. In Claude on the web or desktop, add the connector from the directory and enter your MCP URL.
Some clients cannot connect to localhost. For containerized setups, Metabase says to set MB_SITE_URL. Clients connected before version 0.64 must sign in again after upgrading. Our MCP config generator can help with other clients.
Security notes
Metabase splits access into five OAuth scopes:
| Scope | What it allows |
|---|---|
agent:content:read | Read content and data structure |
agent:query:run | Run queries and see results |
agent:content:write | Create, edit and trash content |
agent:sql:run | Write and run raw SQL |
agent:delivery:write | Create alerts and subscriptions |
Metabase says a scope never grants more than the user's own permissions. execute_sql needs the agent:sql:run scope, a specific MCP setting turned on and the tool enabled for the user's groups. Metabase marks it write-capable because raw SQL can overwrite or delete data. Leave it off unless the database connection itself is read-only.
On Pro and Enterprise, admins can limit tools per group and review MCP analytics. Metabase notes that MCP calls do not appear in AI usage auditing, and error messages show in MCP analytics only when PII retention is on.
Results go to your AI client, which may send them to an AI provider. Collection names and dashboard text written by others can carry hidden instructions. See prompt injection through tool results, MCP tool poisoning and the MCP Security Center.
Alternatives
- Tableau MCP server for Tableau Cloud or Tableau Server.
- Snowflake MCP server to query the warehouse behind your dashboards.
- Google BigQuery MCP server if your data sits in BigQuery.
Next step
Grant agent:content:read and agent:query:run first, and add write scopes once people trust the answers. Compare options in our best MCP servers for data analytics list.
More in the MCP Guide
Free tools: MCP Server Risk Checklist · Tool Permission Planner
Latest research: State of MCP: October 2026
Frequently asked questions
Is the Metabase MCP server available on the open-source edition?
Metabase's MCP docs describe the server without naming a plan. They list per-group tool limits, MCP analytics and headless JWT access as Pro and Enterprise features. Check Metabase's pricing page for your edition.
What URL do I use?
Use your own instance URL plus /api/metabase-mcp, for example https://{your-metabase-url}/api/metabase-mcp. Admins can copy it from the MCP settings page.
Can the AI run raw SQL?
Only if allowed. execute_sql needs the agent:sql:run scope, an admin setting and group access. Metabase marks it write-capable because SQL can change or delete data.
Is the unofficial Metabase connector the same thing?
No. Claude's directory also lists "Metabase (Unofficial, Community)" from a separate developer. This profile covers the official server that ships inside Metabase.











