← All connection guides

How to connect Cursor to Supabase

Connect Cursor to Supabase using the official plugin, or configure a read-only MCP connection for one development project.

Free guide · Updated

Based on official documentation · Checked

Ask your agent

Copy the prompt and paste it into your assistant.

Quick answer

Install the official Supabase plugin from Cursor chat, then authorize its MCP connection. The plugin includes platform tools and Supabase/Postgres skills. For a connection limited to one development project and read-only queries, use a manual MCP entry with the corresponding URL parameters.

1. Install the plugin in Cursor

Open Cursor chat and submit the official plugin command. Review and complete the installation prompt:

/add-plugin supabase

2. Connect your account

Open Cursor Settings → Tools & MCP and inspect the Supabase connection. Follow the sign-in prompt and authorize the account and organization containing your project. Start a fresh agent conversation after installation if tools are not yet discovered.

Manual alternative: one project, read-only

If you prefer MCP without the bundled skills, add a custom server under Tools & MCP. Merge this entry into the existing configuration, replacing YOUR_PROJECT_REF with your project reference. Preserve unrelated servers:

{
  "mcpServers": {
    "supabase": {
      "url": "https://mcp.supabase.com/mcp?project_ref=YOUR_PROJECT_REF&read_only=true"
    }
  }
}

Choose one route

Do not keep duplicate plugin and manual connections unintentionally. The manual URL explicitly scopes the project and database read-only mode; a default plugin installation should not be assumed to apply those restrictions. Review the configuration you actually use.

Practice

3. Retrieve database context

  1. Ask Cursor to use Supabase MCP to list tables, inspect a named development table’s columns and explain how that schema relates to your local application code. Request no SQL changes.

Output: The schema matches the dashboard and Cursor distinguishes retrieved database facts from assumptions about your code.

Troubleshooting

No tools: check installation, connection status and whether the current agent conversation can use MCP. Wrong project: inspect project_ref or the authorized organization. A failed read and an empty table are different results. Reconnect only after identifying the account or permission problem; do not paste a service-role key into chat.

Disconnect

Remove the plugin or manual server you configured and revoke its authorization when appropriate. Keep any Supabase SDK configuration needed by the application itself; that is separate from Cursor’s agent connection.

Sources

Read the primary material