Log inSubmit server
Metabase MCP logo

Metabase MCP

by 1luvc0d3

Connects AI clients to Metabase for guarded SQL, dashboard operations, workflows, and server-side AI analysis.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Metabase MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "1luvc0d3-metabase-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@ai-1luvc0d3/metabase-mcp"
      ],
      "env": {
        "METABASE_URL": "YOUR_VALUE_HERE",
        "METABASE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @ai-1luvc0d3/metabase-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The 1luvc0d3/metabase-mcp MCP server exposes Metabase operations to MCP clients through API-key authentication, supporting headless agents, CI, and self-hosted instances behind a VPN. It provides read, write, and full modes, with SQL safety checks, configurable rate limits, audit logging, batching, workflows, and optional Anthropic-powered NLQ and insight tools. Reach for it when OAuth browser flows are impractical, when you need controlled unattended access, or when your Metabase version predates the official MCP server.

Use cases

  • Query Metabase data from headless agents
  • Run guarded SELECT queries in CI
  • Build multi-step dashboard workflows
  • Generate server-side SQL insights
  • Control agent access with tool policies

Key features

  • Metabase API-key authentication
  • Read, write, and full server modes
  • SELECT-only SQL guardrails
  • Batch and chained workflow execution
  • Tiered rate limiting and audit logging
  • Optional Anthropic-powered analysis

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 50d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @ai-1luvc0d3/metabase-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads74Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity6 viewsConfig copies, upvotes, and views on AllMCPs.

How Metabase MCP works

What 1luvc0d3/metabase-mcp MCP server does

The 1luvc0d3/metabase-mcp MCP server connects an MCP client to a Metabase instance using a Metabase API key. Its tool surface covers reading dashboards, cards, and databases; creating and updating questions, dashboards, and collections; executing SELECT-oriented SQL; and deleting cards or dashboards. It also supports adding and removing cards from dashboards.

The package includes 30 tools across read, batch, workflow, write, natural-language query, and insight functions. Optional Anthropic integration enables natural-language questions that produce SQL and results, along with SQL explanation, optimization, validation, automated insights, and trend analysis. These AI features require an Anthropic API key.

How it works

The server runs locally as an MCP process and sends requests to the configured Metabase URL. API-key authentication makes it suitable for CI and autonomous agents without an OAuth browser flow. It can also connect to self-hosted Metabase deployments that are reachable from the host running the process, including instances behind a VPN.

Three modes control the broad permission set: read is the default, write enables write operations, and full includes AI insight capabilities. MCP_TOOLS_ALLOW and MCP_TOOLS_DENY provide per-tool filtering; deny rules take precedence and also apply to tools nested inside batches and workflows.

batch_execute can run up to 20 parallel operations. run_workflow chains steps and lets later steps reference earlier outputs with expressions such as $stepName.path. Responses use compact JSON by default, while format: "default" requests expanded output. Schema caching supplies context for natural-language queries against larger databases.

Setup and configuration

Install the npm package with npx @ai-1luvc0d3/metabase-mcp, install it globally with npm, or build and start the project from source. Claude Desktop can also install a release .mcpb package and prompt for the Metabase URL and API key, storing those values in the operating system keychain.

The required variables are METABASE_URL and METABASE_API_KEY. Set MCP_MODE to read, write, or full as needed. ANTHROPIC_API_KEY is optional and enables the server-side AI functions. Other settings control request timeout, maximum returned rows, log level, tool allow/deny lists, and separate read, write, and LLM request limits.

Tools and capabilities

SQL execution includes injection detection, DDL/DML blocking, and dangerous-pattern enforcement. Rate limits are configurable independently for read, write, and LLM operations. Each operation is audit-logged with a risk assessment. These controls make the 1luvc0d3/metabase-mcp MCP server suited to deployments where agents need access to BI data without unrestricted tool exposure.

Limitations and notes

Authentication uses an API key rather than OAuth, so the server does not provide OAuth-based per-user permission scoping. It does not provide inline interactive charts rendered in the AI client. The optional natural-language and insight functions depend on Anthropic, and raw query access remains subject to the server's SQL guardrails and configured row limit.

The project is intended to work with Metabase versions older than 0.60 as well as newer versions. Choose the official Metabase MCP server instead when OAuth-based user scoping or inline interactive charts are more important than headless API-key access and the controls provided by the 1luvc0d3/metabase-mcp MCP server.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Metabase MCP

Run `npx @ai-1luvc0d3/metabase-mcp`, install the npm package globally, or download the release `.mcpb` file for Claude Desktop.

`METABASE_URL` and `METABASE_API_KEY` are required. `ANTHROPIC_API_KEY` is optional and enables NLQ and insight tools.

Yes.

Yes. It authenticates to Metabase with an API key, supporting headless agents, CI, and self-hosted instances behind a VPN.

Related MCP servers

All in Data Visualization All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMetabase MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/1luvc0d3-metabase-mcp?style=directory)](https://allmcps.com/mcp/1luvc0d3-metabase-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/1luvc0d3-metabase-mcp"><img src="https://allmcps.com/api/badge/1luvc0d3-metabase-mcp?style=directory" alt="Metabase MCP on AllMCPs" /></a>