Metabase

A Model Context Protocol server for Metabase integration.

This is a TypeScript-based MCP server that implements integration with Metabase API. It allows AI assistants to interact with Metabase, providing access to:

- Dashboards, questions/cards, and databases as resources
- Tools for listing and executing Metabase queries
- Ability to view and interact with Metabase data

- List and access Metabase resources viametabase://URIs
- Access dashboards, cards/questions, and databases
- JSON content type for structured data access

- list_dashboards- List all dashboards in Metabase
- list_cards- List all questions/cards in Metabase
- list_databases- List all databases in Metabase
- execute_card- Execute a Metabase question/card and get results
- get_dashboard_cards- Get all cards in a dashboard
- execute_query- Execute a SQL query against a Metabase database

Before running the server, you need to set environment variables for authentication. The server supports two methods:

- METABASE_URL: The URL of your Metabase instance (e.g.,https://your-metabase-instance.com).
- METABASE_API_KEY: Your Metabase API key.

- METABASE_URL: The URL of your Metabase instance.
- METABASE_USERNAME: Your Metabase username.
- METABASE_PASSWORD: Your Metabase password.

The server will first check forMETABASE_API_KEY. If it's set, API key authentication will be used. IfMETABASE_API_KEYis not set, the server will fall back to usingMETABASE_USERNAMEandMETABASE_PASSWORD. You must provide credentials for at least one of these methods.

# Required environment variables export METABASE_URL=https://your-metabase-instance.com export METABASE_API_KEY=your_metabase_api_key

# Required environment variables export METABASE_URL=https://your-metabase-instance.com export METABASE_USERNAME=your_username export METABASE_PASSWORD=your_password

You can set these environment variables in your shell profile or use a.envfile with a package likedotenv.

# Oneliner, suitable for CI environment git clone https://github.com/imlewc/metabase-server.git && cd metabase-server && npm i && npm run build && npm link

To use with Claude Desktop, add the server config:

On MacOS:~/Library/Application Support/Claude/claude_desktop_config.jsonOn Windows:%APPDATA%/Claude/claude_desktop_config.json

{ "mcpServers": { "metabase-server": { "command": "metabase-server", "env": { "METABASE_URL": "https://your-metabase-instance.com", // Use API Key (preferred) "METABASE_API_KEY": "your_metabase_api_key" // Or Username/Password (if API Key is not set) // "METABASE_USERNAME": "your_username", // "METABASE_PASSWORD": "your_password" } } } }

Note: You can also set these environment variables in your system instead of in the config file if you prefer.

To install metabase-server for Claude Desktop automatically viaSmithery:

npx -y @smithery/cli install @imlewc/metabase-server --client claude

claude mcp add metabase-server -s user \ -e METABASE_URL="https://your-metabase-instance.com" \ -e METABASE_USERNAME="your-email@example.com" \ -e METABASE_PASSWORD="your-password" \ -- npx -y @imlewc/metabase-server

claude mcp add metabase-server -s user \ -e METABASE_URL="https://your-metabase-instance.com" \ -e METABASE_API_KEY="your-api-key" \ -- npx -y @imlewc/metabase-server

{ "mcpServers": { "metabase-server": { "type": "stdio", "command": "npx", "args": ["-y", "@imlewc/metabase-server"], "env": { "METABASE_URL": "https://your-metabase-instance.com", "METABASE_USERNAME": "your-email@example.com", "METABASE_PASSWORD": "your-password" } } } }

If MCP server fails to connect, check the logs:

cat ~/.claude/debug/latest | grep -i metabase

- Environment variables not configured ("env": {}is empty)
- Invalid URL format (must includehttps://)
- Incorrect credentials

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using theMCP Inspector, which is available as a package script:

Maritime intelligence for tracking vessels, analysing ports, and exploring ship data.