Supabase MCP: What It Is and How to Set It Up Safely

Denis Kildishev -

Supabase MCP is the Model Context Protocol server for Supabase. It lets AI assistants such as Cursor, Claude, Windsurf and VS Code Copilot work with a Supabase project directly: list tables, read the schema, run SQL, apply migrations, check logs and manage branches, all from a chat prompt.

For developers building on Supabase, that is a big speed-up. It is also a direct line from a language model to your database, which is why setting it up safely matters more than setting it up quickly.

What the Supabase MCP server can do

  • Explore: list projects, tables, columns and relationships.
  • Query: run SQL against the database.
  • Change schema: create and apply migrations.
  • Debug: read logs and advisor warnings.
  • Develop: generate TypeScript types, manage Edge Functions and branches.
  • Look things up: search Supabase documentation.

How to set it up

  1. Choose the project. Point the server at a development project or a branch, not production.
  2. Add the server to your client. Add the Supabase MCP server to the MCP configuration of Cursor, Claude Desktop or your editor, and sign in with your Supabase account when prompted.
  3. Scope it. Limit the server to a single project and turn on read-only mode unless you need write access.
  4. Test with a harmless prompt. Ask it to list tables and describe one schema before anything else.

Check Supabase's documentation for the current configuration syntax, since options change between releases.

How to use it safely

Do not connect it to production

Supabase's own guidance is to use MCP with development data. An assistant that can run SQL on production can delete or expose real customer data after a single bad prompt.

Use read-only mode

Read-only mode runs queries as a read-only database user. Turn it on by default and switch it off only for deliberate schema work.

Scope to one project

Project scoping stops the assistant from reaching other projects in your organization.

Review tool calls

Keep manual approval of tool calls switched on in your client, so you see each SQL statement before it runs.

Watch for prompt injection

If the assistant reads data that users entered, such as support messages, that text can contain instructions. Treat database content as untrusted input.

Supabase MCP vs a governed app

Supabase MCP is a developer tool: it gives one person, usually an engineer, broad access to a project through an AI assistant. It is not how support, operations or finance teams should work with production data. They need an interface where row-level permissions apply to them, where actions are limited to what their role allows and where every change is logged.

That is the gap Jet Admin fills. Jet connects to Supabase and 200+ other data sources and builds admin panels, internal tools, portals and AI agents on the live data, inside one role model. Granular permissions, SSO and audit logs are on the Business plan and above. See also Supabase GUI tools and MCP security.

Frequently asked questions

What is Supabase MCP?

The official Model Context Protocol server for Supabase, which lets AI assistants query, inspect and manage Supabase projects.

Is Supabase MCP safe to use with production data?

Supabase recommends using it with development projects. If you must connect production, use read-only mode, project scoping and manual approval of every query.

Which AI tools work with Supabase MCP?

Any MCP client, including Cursor, Claude Desktop, Claude Code, Windsurf and VS Code with Copilot.

Can non-developers use Supabase MCP?

It is designed for developers. Business teams are better served by an app with role-based permissions on the same data.

Give your team Supabase data, not Supabase keys

Start with Jet Admin for free and build an internal tool on your Supabase project.