Skip to content
mcp/harbor

VS Code Supabase generate_typescript_types

How to: VS Code Supabase generate_typescript_types

client:VS Code transport:stdio tool:generate_typescript_types

Add Supabase to VS Code

  1. 01

    Open .vscode/mcp.json and merge this in. Keep any servers already there. 

{
  "inputs": [
    {
      "type": "promptString",
      "id": "supabase-access-token",
      "description": "SUPABASE_ACCESS_TOKEN",
      "password": true
    }
  ],
  "servers": {
    "mcp-server-supabase": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@supabase/mcp-server-supabase"
      ],
      "env": {
        "SUPABASE_ACCESS_TOKEN": "${input:supabase-access-token}"
      }
    }
  }
}
  1. 02

    Save the file and restart VS Code.

  2. 03

    Ask for something generate_typescript_types does. VS Code 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.

VS Code prompts for each input the first time the server starts, so no secret is written to the file. VS Code 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