Official Data & Analytics

Supabase

Query and manage Supabase Postgres, logs, and Edge Functions via the official server.

Works with: Claude DesktopClaude CodeCursorWindsurf

Official server · page last edited

How to install the Supabase MCP server

Add this to your Claude Desktop MCP configuration:

Add https://mcp.supabase.com/mcp as a remote MCP server and sign in with your Supabase account (OAuth). Add ?project_ref=<project-ref>&read_only=true to limit it to one project in read-only mode.

Add this to your Claude Code MCP configuration:

Add https://mcp.supabase.com/mcp as a remote MCP server and sign in with your Supabase account (OAuth). Add ?project_ref=<project-ref>&read_only=true to limit it to one project in read-only mode.

Add this to your Cursor MCP configuration:

Add https://mcp.supabase.com/mcp as a remote MCP server and sign in with your Supabase account (OAuth). Add ?project_ref=<project-ref>&read_only=true to limit it to one project in read-only mode.

Add this to your Windsurf MCP configuration:

Add https://mcp.supabase.com/mcp as a remote MCP server and sign in with your Supabase account (OAuth). Add ?project_ref=<project-ref>&read_only=true to limit it to one project in read-only mode.

Built by ContextBoltThis directory is built by ContextBolt: MCP-native memory and SEO tools that run alongside Supabase in the same client.

Explore ContextBolt

The Supabase MCP server gives Claude access to your Supabase project: Postgres queries and migrations, logs, Edge Functions, and docs search. For anyone using Supabase as a backend, this is a direct way to bring your data into Claude.

Supabase’s own server is the canonical install. It lives in the supabase/mcp repository and runs as a hosted endpoint at https://mcp.supabase.com/mcp.

Why use it

Supabase is one of the most popular backends for solo founders and small teams. The flip side: when something breaks in production, you’re still flipping between the Supabase dashboard, your editor, and the deployed app. The MCP server collapses the dashboard piece.

Common pattern: a user reports a bug, Claude pulls the relevant rows from your Supabase Postgres, identifies the issue, drafts a SQL fix or an app code change. End-to-end debug from a prompt.

What it actually does

Database: list tables, run SQL, apply migrations. Debugging: query logs and run security and performance advisors. Development: fetch project URLs and generate TypeScript types. Edge Functions: deploy and manage them. Storage tools exist but are off by default.

Practical patterns:

  • “How many users signed up this week and what are their plans?”
  • “Run the security advisor on my project and summarise what it flags.”
  • “Pull the last 50 records from the events table where source = ‘webhook’.”

Gotchas

The server acts with your Supabase account’s access, so Claude can reach whatever you can. For production projects, scope the connection to one project (project_ref), turn on read-only mode, and restrict the feature groups. Better still, run it against a development branch.

Log access sits in the debugging tool group. If logs are a key part of your debug flow, check that group is enabled for your connection.

Pair with Vercel or Cloudflare for a full app-stack debug loop: deployment health from the host, app errors from the database. Add GitHub and Claude can also propose code fixes for the issues it finds.

For users who only need raw Postgres access (no Storage, no Auth), the Postgres MCP server is a lighter alternative. Pointed at your Supabase connection string, it works the same as any other Postgres database.

Built by ContextBolt

This directory is built by ContextBolt

We build MCP-native tools that give your AI the context it cannot reach on its own. Bookmarks turns your saved posts into agent-queryable memory. SEO puts live keyword and ranking data inside Claude. Both run alongside Supabase in the same client.

Explore the products →

Supabase MCP server: FAQs

Is the Supabase server official?

Yes. The source now lives in Supabase's own repository, supabase/mcp, and Supabase runs a hosted server at https://mcp.supabase.com/mcp. The old supabase-community repository address redirects there.

What does it actually expose?

Tools are grouped into database (tables, migrations, SQL), debugging (logs and advisors), development (project URLs, keys, type generation), Edge Functions, account management, docs search, branching on paid plans, and Storage, which is off by default. There are no tools for managing your app's auth users. That is wider than a standalone Postgres server.

Does it bypass Row Level Security?

The hosted server signs in with your Supabase account through OAuth, so it acts as you rather than as your app's users. Supabase's guidance is to connect to a production project only when the task needs it, and to use project scoping, read-only mode (read_only=true) and restricted feature groups. Personal access tokens are the fallback for CI or clients without OAuth support.

Can it write to my database?

Yes, unless you turn on read-only mode. The database tools can run SQL and apply migrations. That is useful for fixtures and one-off corrections, but be careful about destructive prompts.

How is this different from the Postgres MCP server pointed at Supabase?

The Postgres MCP server in this directory is read-only, archived, and gives you raw SQL. The Supabase server adds migrations, logs, advisors, Edge Functions and docs search. If you're using Supabase's full feature set, install this one. If you only use the Postgres database, a plain Postgres server is simpler.