Supabase MCP Server

Overview

Supabase MCP Server is Supabase's own hosted MCP endpoint for managing a Supabase project without leaving your AI client. It's a single URL you connect to, with no local process to run, since Supabase runs the server side for you.

How it works

1. Connecting to mcp.supabase.com/mcp triggers an OAuth login, and you pick which Supabase organization and project the client should have access to.
2. It covers project-level management: creating and inspecting tables, reading configuration, and running queries against your database through natural language rather than the SQL editor.
3. A project_ref parameter and a read_only flag on the connection URL let you scope a client to one specific project and, optionally, block every write-capable tool for that connection.
4. Self-hosted and local (Supabase CLI) Supabase instances also expose an MCP endpoint, though currently with a smaller set of tools and without OAuth, since there's no central Supabase account involved.
5. The repository also ships a separate PostgREST MCP server as a companion package, for exposing your own REST API to your own users' agents rather than managing the Supabase project itself.

Examples

"Connect to my Supabase project and show me the schema of the orders
table, then write a query that finds orders with no matching customer
record."

Notes

Supabase's own security guidance recommends reading their MCP security best practices before connecting an agent to a real project, since the server can read and modify live data depending on the scopes you grant it.

Installation

Nothing runs locally, this is a remote, Supabase-hosted server. You just need an MCP client that supports HTTP servers and a Supabase account.

1. Add the server to your MCP client's config using the block in the sidebar.
2. Restart your client. It opens a browser window for OAuth login.
3. Pick which Supabase organization and project the client should access.
4. Optional: add a project_ref and read_only=true to the URL to scope the connection to one project or block writes.
5. Read Supabase's own MCP security guidance before connecting it to a project with real data.