The official Gemini CLI extension for Metabase. Developed and maintained by the Metabase Team.
- Extension manifest:
gemini-extension.json(declares themetabaseUrlsetting + the Metabase MCP server) - Context file:
GEMINI.md(tells Gemini when to use the Metabase MCP and what not to do)
Current scope: manifest + MCP config + context file only (no agent skills, commands, or hooks yet).
- Gemini CLI with extension support.
- A Metabase instance on version 60 or higher with the MCP server enabled (it ships enabled by default in 60+).
gemini extensions install https://github.com/metabase/metabase-gemini-extensionGemini will prompt for metabaseUrl during install — paste your Metabase base URL (e.g. https://metabase.acme.com or http://localhost:3000, no trailing slash).
After installing, open gemini and run this once to authorize:
/mcp auth metabase
This opens your browser for the Metabase OAuth handshake. Approve, and the token is cached for subsequent calls. After that you can ask things like "what tables do I have in Metabase?" and the agent will use the MCP tools.
Note: Gemini CLI does not currently kick off OAuth automatically for streamable-HTTP MCP servers, so
gemini mcp listwill showDisconnecteduntil you run/mcp auth metabaseonce. You only need to do this once; tokens are cached. Tracking issues: google-gemini/gemini-cli#19068, #20017, #20990, #23296, #25473.
gemini extensions set metabase.metabaseUrl https://metabase.new-host.com-
Clone this repo.
-
Link it into Gemini as a local development extension:
gemini extensions link /path/to/metabase-gemini-extension
-
Gemini will prompt for the
metabaseUrlsetting (paste any reachable Metabase URL). -
Start a Gemini chat and ask it to query something in Metabase — the first call triggers OAuth in your browser.
Sister projects from the Metabase Team:
MIT