Query MCP for Supabase for Cursor: Setup & Config

What you can do with Query MCP for Supabase in Cursor

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

• Administer hosted Supabase projects through the Management API.
• Manage users through Supabase Auth Admin methods.

Before you start: Query MCP for Supabase in Cursor

• 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 Cursor configuration

1. Choose Cursor configuration scope

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

2. Add Query MCP for Supabase to Cursor

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

3. Check Query MCP for Supabase in Cursor

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

{
  "mcpServers": {
    "supabase-mcp-server": {
      "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 Cursor

• Cursor must find uv for Query MCP for Supabase. Enable the project/user entry in MCP settings and inspect its tools.
• Review QUERY_API_KEY, SUPABASE_ACCESS_TOKEN, SUPABASE_DB_PASSWORD, SUPABASE_PROJECT_REF, SUPABASE_REGION, SUPABASE_SERVICE_ROLE_KEY for Query MCP for Supabase before sharing project .cursor/mcp.json; project scope travels with the repository.
• Query MCP for Supabase uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions