Supabase MCP Server
Supabase's official MCP server: the agent manages tables, reads project config and queries data after an OAuth login
- 2,982 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- Can change schema and data in a cloud database
- Gets account access via OAuth
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/supabase-mcp-serverDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Can change schema and data in a cloud database
- Gets account access via OAuth
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to Supabase projects so it can work with tables, fetch project settings and query data. The main option is hosted by Supabase over HTTP, with an OAuth login during first setup. URL parameters restrict the server to one project, read-only mode and specific tool groups. The local Supabase CLI stack and self-hosted installs have their own endpoint with a reduced tool set. The npm package also exports helpers for the Vercel AI SDK and for serving the tools from your own endpoint.
Who it is for. For developers with a Supabase backend who want to manage the database and project through an agent.
Good fit when
- You want the agent to create or change tables in a Supabase dev project
- You need project config or data without opening the dashboard
- You want to wire Supabase tools into your own Vercel AI SDK app
Not a fit when
- A project with production data without read-only mode
- The database is not on Supabase: plain Postgres needs a different server
Example request
Create a comments table linked to posts in my Supabase project and enable RLS on itMCP
- Transport
- http
- Authentication
- OAuth
Limitations
Requires a Supabase account and an OAuth login. Supabase itself recommends reading its security risks guide and keeping the agent away from production projects. Local and self-hosted modes have fewer tools and no OAuth. Access to Supabase cloud from Russia without a VPN is not guaranteed.
How to disable. Remove the supabase server from the MCP client config and revoke the app's access in your Supabase account settings.
FAQ
Can I stop the agent from modifying data?
Yes, read_only=true in the server URL leaves only read tools, and project_ref limits access to one project.
Does it work with local Supabase?
Yes, with Supabase CLI the server is at http://localhost:54321/mcp, with a subset of tools and no OAuth.
Discussion
No questions or reviews yet.
Related
MCP serversSupabase's official CLI: local stack, database migrations, Edge Functions deploys and type generation from the terminal
Apollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
Supabase's official skills: help an agent work with the database, Auth, Edge Functions and Postgres best practices
Two official Prisma MCP servers: a local one for migrations and Prisma Studio, and a remote one for managing Prisma Postgres databases
Instant REST and MCP over PostgreSQL: the agent reads an existing database through an MCP endpoint with no backend to write
A PostgreSQL MCP server with index tuning, EXPLAIN plans, database health checks and a read-only mode
README in short
The README opens by urging you to read the security guidance, then gives JSON for the remote server and a link to the URL builder in the dashboard. It covers Supabase CLI and self-hosted variants. Most of the text is about the npm package: tool schemas for Vercel AI SDK and a handler for your own HTTP endpoint. A separate PostgREST server is also mentioned. Apache 2.0 licensed.