Skip to content
mcp/harbor

Gemini CLI Supabase execute_sql

How to: Gemini CLI Supabase execute_sql

client:Gemini CLI transport:stdio tool:execute_sql

Add Supabase to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "mcp-server-supabase": {
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase"
      ],
      "env": {
        "SUPABASE_ACCESS_TOKEN": "<SUPABASE_ACCESS_TOKEN>"
      }
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something execute_sql does. Gemini CLI lists the server's tools on connect and calls execute_sql itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Supabase's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Supabase will not start until these are set, so execute_sql never becomes available.

  • SUPABASE_ACCESS_TOKEN

Same tool, other clients

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Supabase MCP server