Pod to App: Cursor
How to install the Supabase MCP server in Cursor
By Sophie Filer · Updated 11 Nov 2026 · Steps checked against Supabase's own docs on 11 Nov 2026
The short answer
Add a supabase entry pointing at https://mcp.supabase.com/mcp to .cursor/mcp.json, save, and Cursor sends you to Supabase to sign in. Add ?project_ref=...&read_only=true to the URL to keep it to one project and read-only.
{
"mcpServers": {
"supabase": {
"url": "https://mcp.supabase.com/mcp?project_ref=YOUR_PROJECT_REF&read_only=true"
}
}
}- File
- .cursor/mcp.json
- Sign-in
- Supabase account in the browser
- Check
- Settings › Tools & MCP
- Price
- Free, Apache 2.0
Set it up step by step
- Step 1: Find your project ref: the short ID in the dashboard URL,
supabase.com/dashboard/project/<ref>. - Step 2: Create
.cursor/mcp.jsonin your project (or open it) and paste the block at the top of this page with your ref in place. - Step 3: Save. Cursor opens a browser window to sign in to Supabase. Pick the organisation that owns the project and grant access.
- Step 4: Go to Settings, Cursor Settings, Tools & MCP and check supabase is connected with its tools. Restart Cursor if tools are missing.
- Step 5: In an Agent chat, ask: "What tables are in my database? Use MCP tools."
One project or all of them
| File | Effect |
|---|---|
.cursor/mcp.json in the repo | Supabase tools only in this project, the natural fit when the ref matches this app |
~/.cursor/mcp.json | Supabase in every project you open; leave out project_ref only if you really want access to all your projects |
Neither file holds a secret, since sign-in happens in the browser, so the project file is safe to commit for the team.
Manage it from the Cursor CLI
Cursor's command line agent shares the same MCP configuration as the editor. Supabase's guide lists the commands to approve, sign in and check the server from a terminal:
agent mcp enable supabase
agent mcp login supabase
agent mcp listPick the tools it gets
Add features= to the URL to choose tool groups, for example &features=database,docs,debugging. Groups include account, database, debugging, development, docs, functions, branching and storage. Storage is off unless you name it.
Keep your data safe
Supabase's own example of the risk is a support ticket that contains hidden instructions; when you ask Cursor to read the ticket, the agent may try to follow them. Their advice:
- Keep manual approval of tool calls on, and read each SQL query before it runs.
- Prefer a development project or a branch over production.
- Use
read_only=trueunless you need writes. - Never give this setup to your own users; it acts with your developer permissions.
Troubleshooting
| What you see | What to do |
|---|---|
| No sign-in window appeared | Toggle supabase off and on in Tools & MCP, or run agent mcp login supabase. |
| Signed in but your project is missing | You chose a different organisation. Clear the sign-in and pick the one that owns the project. |
| Tools listed, but writes fail | Expected with read_only=true. Remove it only on a development project or branch. |
| Tools appear only after a restart | Normal for some setups: restart Cursor after the first sign-in. |
MCP Shelf take
Is Supabase worth adding to Cursor?
Cursor plus Supabase is a strong everyday pairing: the agent can look at your real schema before it writes a query, generate a migration that fits, and check the security advisors when you add a table. The setup is light because it is hosted and signs in through the browser. The one thing to get right is scope. Put the project ref and read-only in the URL from day one, commit that file, and only open up writes on a branch you can throw away.
Sophie Filer
Questions
Do I need a Supabase access token in Cursor?
No. Cursor signs you in to Supabase in the browser. Tokens are only for places where no one can sign in, such as CI.
Where do I check the Supabase MCP connection in Cursor?
Settings, Cursor Settings, Tools & MCP. The supabase entry should show as connected with its tools listed.
Can Cursor change my Supabase database?
Only without read_only=true in the URL. With it, SQL runs as a read-only Postgres user and write tools are hidden.
Sources: the steps on this page are written in our own words from Supabase's own install docs, the README, the README. If they disagree with this page, the project's docs win; please tell us from the server page.
