1. Home
  2. Supabase MCP Server
  3. Supabase MCP Server for VS Code: Setup & Config

Data as of

Supabase MCP Server for VS Code: Setup & Config

Connect VS Code to Supabase projects for SQL, schema changes, debugging, and Edge Functions.

Supabase MCP Server VS Code configuration

  1. Choose VS Code configuration scope

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

  2. Add Supabase MCP Server to VS Code

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

  3. Check Supabase MCP Server in VS Code

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

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "supabase-mcp": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

Supabase in VS Code: http checks

  • The Supabase MCP Server entry connects to mcp.supabase.com with type http. Start it through VS Code's MCP controls and review the endpoint before accepting trust prompts.
  • Supabase MCP Server: check http connectivity to mcp.supabase.com from VS Code; a stdio command is not a replacement for this endpoint.
Catalog transports
stdio
Tools
search_docs, list_organizations, get_organization

Supabase MCP Server — details. VS Code guide

Frequently asked questions

For Supabase MCP Server, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's supabase-mcp example uses http. The Supabase MCP Server catalog lists stdio; these instructions follow the stored configuration instead.

VS Code connects Supabase MCP Server to mcp.supabase.com using url.

Supabase MCP Server's stored list contains 33 tools, including search_docs, list_organizations, get_organization. Compare those names with VS Code's connected tool list; the stored list is not a live check.