Does Cursor integrate with Supabase?
Yes — via the official Supabase MCP server
Yes. Cursor connects to Supabase through Supabase's official MCP server. You add the server in Cursor's Tools & MCP settings, then a browser OAuth login links your Supabase account. Cursor can then read your schema, run queries, apply migrations and deploy Edge Functions. The free tiers on both sides are enough, and read-only mode is available.
| Integration method | Native via MCP — Cursor connects to Supabase through Supabase's official hosted MCP server. You add the server in Cursor Settings > Tools & MCP, and Cursor authenticates to Supabase with a browser OAuth login (no manual personal access token needed for normal use). No Zapier or Make is involved. |
|---|---|
| Sync direction | Two-way by default: Cursor can read your schema, run SQL, apply migrations and deploy Edge Functions. Add the read_only=true parameter to restrict it to read-only queries. |
| Plan required | Cursor: any plan, including the free tier. Supabase: works on the free tier; only branching-related tools require a paid Supabase plan. |
| Setup time | ~5 minutes unverified estimate |
How to connect Cursor to Supabase
- In Cursor, open Settings > Cursor Settings > Tools & MCP and add the Supabase MCP server using Supabase's install instructions.
- When prompted, complete the browser OAuth login to Supabase and authorize the MCP client.
- Optionally scope the server with project_ref=<your-project-id> and add read_only=true if you only want read access.
- Back in Tools & MCP, confirm the Supabase server shows as connected.
- Test it by asking Cursor: "What tables are there in the database? Use MCP tools." and approve the tool call.
Known friction points
- Some users hit a "no proper authentication" error where the tools refuse to reach the Supabase account even after supplying a token; re-running the OAuth login or pasting the authorization URL from Cursor's Output log into a browser is the commonly reported workaround. [source]
- The OAuth flow sometimes fails to trigger automatically; users report finding the https://api.supabase.com/v1/oauth/authorize... URL in Cursor's Output panel and opening it manually to finish authentication. [source]
FAQ
- Does Cursor integrate with Supabase?
- Yes. Cursor connects to Supabase through Supabase's official MCP server. Once added in Cursor's Tools & MCP settings and authorized via OAuth, Cursor can read your schema, run SQL, apply migrations and deploy Edge Functions.
- Do I need a paid plan to connect Cursor to Supabase?
- No. Cursor's free tier and Supabase's free tier are enough. Only branching-related MCP tools require a paid Supabase plan.
- Can I make the connection read-only so Cursor can't change my database?
- Yes. Add the read_only=true parameter when configuring the Supabase MCP server and all operations run as a read-only Postgres user.
✓ Last verified: 2026-06-10 · Every claim on this page links to a primary source. If the integration changed, the page is out of date — check the sources below.
Sources
- Supabase docs — MCP server setup (accessed 2026-06-10)
- Supabase Discussion #35317 (authentication error) (accessed 2026-06-10)
- Supabase Discussion #39266 (OAuth not triggering) (accessed 2026-06-10)