Backend integration layer that connects your Metabase instance with AI assistants using the Model Context Protocol (MCP)
Backend integration layer that connects your Metabase instance with AI assistants using the Model Context Protocol (MCP). The 📊 metabase mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Instead of navigating through menus or constructing SQL queries manually, you can:
Everything the assistant can do here goes through one of these:
Function — Descriptionget_metabase_collection — Get a collection by IDcreate_metabase_collection — Create a new collectionupdate_metabase_collection — Update collection metadatadelete_metabase_collection — Delete a collectionget_metabase_cards — List all chartsget_card_query_results — Get results from a chart querycreate_metabase_card — Create a new chartupdate_metabase_card — Update an existing chartdelete_metabase_card — Delete a chartget_metabase_dashboards — List all dashboardsget_dashboard_by_id — Get a dashboard by IDYou will need 7 environment variables: METABASE_URL, METABASE_API_KEY, HOST, TRANSPORT, LOG_LEVEL, YOUR_API_KEY, FULL_PATH. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
First, install Node.js if you haven't already: - Download from: nodejs.org - Or install via package manager:
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. 📊 Metabase's toolset — Function, get_metabase_collection, create_metabase_collection and 11 more — is a fair guide to whether it matches your workflow. It is maintained by CW-Codewalnut; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Function | Description |
| get_metabase_collection | Get a collection by ID |
| create_metabase_collection | Create a new collection |
| update_metabase_collection | Update collection metadata |
| delete_metabase_collection | Delete a collection |
| get_metabase_cards | List all charts |
| get_card_query_results | Get results from a chart query |
| create_metabase_card | Create a new chart |
| update_metabase_card | Update an existing chart |
| delete_metabase_card | Delete a chart |
| get_metabase_dashboards | List all dashboards |
| get_dashboard_by_id | Get a dashboard by ID |
| get_dashboard_cards | Get cards in a dashboard |
| get_dashboard_items | Get all dashboard items |
Mac:
```json
{
"mcpServers": {
"metabase": {
"type": "stdio",
"command": "/Users/YourName/Projects/metabase-mcp-server/.venv/bin/python",
"args": [
"/Users/YourName/Projects/metabase-mcp-server/src/metabase_mcp_server.py"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
First, install Node.js if you haven't already: - Download from: nodejs.org - Or install via package manager:
| Variable | Description | Required |
|---|---|---|
| METABASE_URL | Endpoint or connection string the server talks to. | Yes |
| METABASE_API_KEY | Credential the server authenticates with. | Yes |
| HOST | Endpoint or connection string the server talks to. | Optional |
| TRANSPORT | Configuration value read at startup. | Optional |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
| FULL_PATH | Filesystem location the server is allowed to use. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.