Gemini CLI Supabase deploy_edge_function

How to: Gemini CLI Supabase deploy_edge_function

client:Gemini CLI transport:stdio tool:deploy_edge_function

Add Supabase to Gemini CLI

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>"
      }
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something deploy_edge_function does. Gemini CLI lists the server's tools on connect and calls deploy_edge_function itself — you do not invoke it by name.
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 deploy_edge_function 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