Skip to content
mcp/harbor

Windsurf Supabase deploy_edge_function

How to: Windsurf Supabase deploy_edge_function

client:Windsurf transport:stdio tool:deploy_edge_function

Add Supabase to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.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 Windsurf.

  2. 03

    Ask for something deploy_edge_function does. Windsurf lists the server's tools on connect and calls deploy_edge_function 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.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf 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