Access your Metabase dashboards, questions, and collections from any MCP-compatible AI client. Run queries, browse data, search analytics. Set up once, works everywhere.
Paste the snippet into your client's config file. OAuth sign-in handles the rest.
{
"mcpServers": {
"metabase": {
"command": "npx",
"args": ["mcp-remote", "https://metabase-mcp.internal.allocate.biz/mcp"]
}
}
}claude mcp add metabase https://metabase-mcp.internal.allocate.biz/mcp{
"mcpServers": {
"metabase": {
"url": "https://metabase-mcp.internal.allocate.biz/mcp"
}
}
}{
"servers": {
"metabase": {
"type": "http",
"url": "https://metabase-mcp.internal.allocate.biz/mcp"
}
}
}[mcp_servers.metabase]
url = "https://metabase-mcp.internal.allocate.biz/mcp"1. Open Settings → Apps & Connectors
2. Click Create
3. Paste the connector URL below
https://metabase-mcp.internal.allocate.biz/mcpCopy the config snippet above into your AI client's settings.
A browser window opens for Google sign-in. Only minimal scopes are requested.
Your AI client can now browse dashboards, run questions, and search your Metabase collections.
Browse dashboards, run questions, and search your Metabase instance.
Only the narrowest Google scopes are requested for sign-in. All Metabase access is read-only.
Proof Key for Code Exchange prevents interception attacks. No client secrets stored on your device.
Google refresh tokens are encrypted at rest with AES-256-GCM before being stored in the database.
Access tokens expire after one hour. Compromised tokens have a limited window of exposure.