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

Data as of

Supabase MCP Server for Cursor: Setup & Config

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

Supabase MCP Server Cursor configuration

  1. Choose Cursor configuration scope

    For Supabase MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

  2. Add Supabase MCP Server to Cursor

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

  3. Check Supabase MCP Server in Cursor

    Supabase MCP Server: Enable in Cursor’s MCP settings; inspect tools.

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

JSON
{
  "mcpServers": {
    "supabase-mcp": {
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

Supabase in Cursor: http checks

  • Enable Supabase MCP Server in Cursor's MCP settings and inspect its tools. For mcp.supabase.com, check reachability, transport, and credential expiry if authentication fails.
  • Supabase MCP Server: check http connectivity to mcp.supabase.com from Cursor; a stdio command is not a replacement for this endpoint.
Catalog transports
stdio
Tools
search_docs, list_organizations, get_organization

Supabase MCP Server — details. Cursor guide

Frequently asked questions

Cursor's Supabase MCP Server entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.

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

Cursor 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 Cursor's connected tool list; the stored list is not a live check.