metabase-mcp
Query your Metabase with AI agents. No API key. No admin begging. Just vibes and a cookie.
The problem
The official Metabase MCP wants an API key or your username/password. Cool in theory. Not so cool if your company won't give you one.
Potencia tu agente
Instalación del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
Aún no hay una versión empaquetada en el registro. Sigue el README del repositorio.
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Query your Metabase with AI agents. No API key. No admin begging. Just vibes and a cookie.
The official Metabase MCP wants an API key or your username/password. Cool in theory. Not so cool if your company won't give you one.
Metabase MCP server for AI Agents. Authenticate with a browser session cookie, no API key required.
But you can log into Metabase in a browser. Which means you have a session cookie. Which means you have everything you need.
That's this.
Honest answer: if you have an API key or username/password, just use the official Metabase MCP. It's proper, supported, and won't expire on you mid-conversation. Newer versions of Metabase also support Google login natively via the official MCP.
This project is for the rest of us: the people whose company guards API keys like they're nuclear launch codes and treats every Metabase upgrade request like a 6-month procurement process.
You'll love this if:
You should know:
go install github.com/Naveen-chava/metabase-mcp@latest
This puts the binary in ~/go/bin/. Make sure that's in your $PATH:
export PATH="$PATH:$(go env GOPATH)/bin"
Or build from source:
git clone https://github.com/Naveen-chava/metabase-mcp
cd metabase-mcp
go install .
This is the one slightly sneaky step.
metabase.SESSION and copy its valueThat's your cookie. Treat it like a password; it grants the same access as your login session.
If the MCP starts throwing 401s, your session expired. Grab a fresh cookie and you're back.
Inline (quick start):
METABASE_URL=https://metabase.company.com \
METABASE_SESSION=your-cookie \
./metabase-mcp
Via file (recommended, no restart when your cookie expires):
echo "your-cookie" > ~/.metabase-session
METABASE_URL=https://metabase.company.com \
METABASE_SESSION_FILE=~/.metabase-session \
./metabase-mcp
To rotate a stale cookie, just overwrite the file. No restart needed; the next request picks it up automatically.
The server expands
~and$HOMEin the session file path, so~/.metabase-sessionworks everywhere.
Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"metabase": {
"command": "metabase-mcp",
"env": {
"METABASE_URL": "https://metabase.company.com",
"METABASE_SESSION_FILE": "~/.metabase-session"
}
}
}
}
Restart Claude Desktop. Done.
claude mcp add metabase metabase-mcp -s user -e METABASE_URL=https://metabase.company.com -e METABASE_SESSION_FILE=~/.metabase-session
Run as a single line. Backslash continuations can introduce invisible characters when copied from some terminals or browsers.
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project-level):
{
"mcpServers": {
"metabase": {
"command": "metabase-mcp",
"env": {
"METABASE_URL": "https://metabase.company.com",
"METABASE_SESSION_FILE": "~/.metabase-session"
}
}
}
}
Restart Cursor and verify the server is connected under Settings → MCP.
metabase-mcp/
├── main.go # Startup, env vars, wires everything together
└── internal/
├── metabase/ # Metabase API client
│ ├── client.go # HTTP client with cookie auth
│ ├── types.go # API types
│ ├── databases.go
│ ├── collections.go
│ ├── cards.go
│ ├── dashboards.go
│ ├── tables.go
│ ├── search.go
│ ├── query.go
│ └── tests/ # HTTP-level tests (package metabase_test)
└── tools/ # MCP tool handlers
├── client.go # MetabaseClient interface
├── register.go # One place to add/remove tools
├── helpers.go # Shared utilities
├── databases.go
├── collections.go
├── cards.go
├── dashboards.go
├── tables.go
├── search.go
├── query.go
└── tests/ # Handler tests with mock client (package tools_test)
go test ./...
Metabase MCP server for AI Agents. Authenticate with a browser session cookie, no API key required.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Metabase se ejecuta localmente por stdio.
Última comprobación: 2026-10-28. Metabase MCP server for AI Agents. Authenticate with a browser session cookie, no API key required.