Skip to content
mcp/harbor

Zed Supabase generate_typescript_types

How to: Zed Supabase generate_typescript_types

client:Zed transport:stdio tool:generate_typescript_types

Add Supabase to Zed

  1. 01

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

{
  "context_servers": {
    "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 Zed.

  2. 03

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

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

Supabase will not start until these are set, so generate_typescript_types 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