Supabase MCP Server

The Supabase MCP Server wires a whole Supabase project into your AI: table schemas, SQL queries, Edge Functions, logs, and migrations. You stop switching to the Dashboard just to check what a table looks like.

It shines during incident triage — ask "how many inserts into users failed in the last hour?" and the AI checks the logs and tables itself instead of you clicking through the Dashboard.

See this server's health data →

What it does for you

Connects your AI straight to your Supabase project — query data, run SQL, inspect schemas, even manage the DB, without leaving the chat.

Capabilities

Query tables and run SQL
Inspect table structure / schema
Manage projects and databases

Once installed, try asking your AI

Say this directly in Claude / Cursor or any client with this server connected

›“Show me the 10 most recently registered users in the users table”
›“What's this month's total order revenue? Break it down by day”

Install / Connect

claude mcp add mcp-server-supabase -- npx -y @supabase/mcp-server-supabase

Follow the official README; env and args vary per server.

Works with these clients

Claude Desktopnpx
Claude Codenpx
Cursornpx
VS Codenpx
Windsurfnpx

Derived from the registry manifest (package type and transport) — we have not installed it ourselves. Check the official README before relying on it.

Why use it

Good for: people running Supabase as their backend who live in Cursor or Claude Code.

Before connecting: the official docs explicitly recommend **not** pointing it at production — use read-only mode and a development branch. It can run SQL, so a badly worded prompt can mutate data.