Query MCP for Supabase for VS Code: Setup & Config

What you can do with Query MCP for Supabase in VS Code

Supabase SQL and administration in one stdio server, with explicit query-risk controls.

• Run SQL from an MCP-enabled IDE.
• Administer hosted Supabase projects through the Management API.

Before you start: Query MCP for Supabase in VS Code

• Python 3.12+
• uv for this launch command
• Install the supabase-mcp-server package
• A Supabase hosted project or local development instance

The README installs the package with uv pip install supabase-mcp-server before launching it. Packaged installs do not load project-local .env files. Claude Desktop requires an absolute executable path. Active maintenance has ended.

Query MCP for Supabase VS Code configuration

1. Choose VS Code configuration scope

   For Query MCP for Supabase, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Query MCP for Supabase to VS Code

   Use the supabase-mcp-server entry below in servers. Keep Query MCP for Supabase's documented stdio connection fields and your other VS Code entries.

3. Check Query MCP for Supabase in VS Code

   Query MCP for Supabase: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "supabase-mcp-server": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "supabase-mcp-server"
      ],
      "env": {
        "QUERY_API_KEY": "<API key from thequery.dev>",
        "SUPABASE_PROJECT_REF": "<Project reference or local host and port>",
        "SUPABASE_DB_PASSWORD": "<Database password>",
        "SUPABASE_REGION": "<Hosting region for a remote project>",
        "SUPABASE_ACCESS_TOKEN": "<Optional Management API access token>",
        "SUPABASE_SERVICE_ROLE_KEY": "<Optional Auth Admin service-role key>"
      }
    }
  }
}

Troubleshooting Query MCP for Supabase in VS Code

• Make uv available in the workspace, container, or remote environment hosting Query MCP for Supabase. Start through VS Code's MCP controls; inspect output and trust prompts.
• For Query MCP for Supabase, keep QUERY_API_KEY, SUPABASE_ACCESS_TOKEN, SUPABASE_DB_PASSWORD, SUPABASE_PROJECT_REF, SUPABASE_REGION, SUPABASE_SERVICE_ROLE_KEY out of version control; VS Code documents input variables and secret handling.
• Query MCP for Supabase uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: No longer actively maintained by its author.
• Known limitation: Requires a separate Query API key.
• Known limitation: Does not support arbitrary connection strings or session pooling.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions