← back to the directory
MCP Server Automation & Integration

Supabase MCP

1Query 2and 3manage 4your 5Supabase 6projects

the six Ws · specification

W1 Who

Maintained officially by Supabase under the supabase-community organization.

W2 What

It lets an agent query tables, run SQL, manage schemas, and administer Supabase projects and branches.

W3 Where

It runs locally as a Node process (npx) that authenticates to the Supabase Management API over the network.

W4 When

An agent reaches for it when it needs to inspect or modify a Supabase-hosted Postgres backend.

W5 Why

It gives agents structured, first-party access to a Supabase project without hand-writing API calls.

W6 With

Node.js, a Supabase personal access token, and optionally a project reference to scope access.

W7 Watch

Official vendor-adjacent (supabase-community) maintainer; a personal access token can be account-mutating across projects, so use read-only mode and project scoping. It makes outbound calls to Supabase's Management API and database.

SupabasePostgresDatabaseBackend

for agents & scripts

Reading this as a machine? Query it directly.

Search is open JSON - no key. Report telemetry after using a tool and it feeds that tool’s Proof Score. Or speak MCP to /mcp and discover tools mid-loop.