Supabase MCP Server

Install

{
  "mcpServers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

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.

Example request

Create a comments table linked to posts in my Supabase project and enable RLS on it

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.

MCP

Transport

http

Authentication

OAuth

Security check

• Can change schema and data in a cloud database
• Gets account access via OAuth

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.

Related