Log inSubmit server
Supabase MCP Server logo

Supabase MCP Server

by alexanderzuev

Supabase MCP server for SQL, schema changes, Management API operations, and Auth Admin tasks over stdio.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Supabase MCP Server

Pick your client, then add it in one click or paste the config.

STDIOPython
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "alexanderzuev-supabase-mcp-server": {
      "command": "uvx",
      "args": [
        "supabase-mcp-server"
      ],
      "env": {
        "SUPABASE_PROJECT_REF": "YOUR_VALUE_HERE",
        "SUPABASE_DB_PASSWORD": "YOUR_VALUE_HERE",
        "SUPABASE_REGION": "YOUR_VALUE_HERE",
        "SUPABASE_ACCESS_TOKEN": "YOUR_VALUE_HERE",
        "SUPABASE_SERVICE_ROLE_KEY": "YOUR_VALUE_HERE",
        "QUERY_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

uvx supabase-mcp-server

Downloading cpython-3.12.14-linux-x86_64-gnu (download) (32.6MiB) Downloaded cpython-3.12.14-linux-x86_64-gnu (download) Downloading pygments (1.2MiB) Downloading cryptography (4.5MiB) Downloading asyncpg (3.4MiB) Downloading pglast (6.0MiB) Downloading pydantic-core (2.0MiB) Downloaded pydantic-core Downloaded pygments Downloaded asyncpg Downloaded cryptography Downloaded pglast Installed 76 packages in 38ms Traceback (most recent call last): File "/home/user/.cache/uv/archive-v0/5Zeucg

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The alexanderzuev/supabase-mcp-server MCP server connects MCP clients to Supabase PostgreSQL, project management, and Auth Admin capabilities. It supports SQL execution with read-only or read-write modes, runtime risk assessment, transaction handling, and schema-change versioning. Management API and Auth Admin features require their respective Supabase credentials, while all operations require a QUERY_API_KEY from thequery.dev. Reach for the alexanderzuev/supabase-mcp-server MCP server when an IDE or compatible MCP client needs controlled database work against a local or remote Supabase project, but note that the project is no longer actively maintained.

Use cases

  • Run controlled SQL queries from an MCP-compatible IDE
  • Explore and version a Supabase database schema
  • Manage remote Supabase projects through the Management API
  • Administer Supabase users with Auth Admin methods

Key features

  • Read-only and read-write SQL modes
  • Runtime SQL risk assessment
  • Three-tier SQL safety controls
  • Schema exploration and versioning
  • Supabase Management API access
  • Auth Admin SDK user management

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

29/29 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · supabase-mcp-server (PyPI)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars833Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity1 upvotesConfig copies, upvotes, and views on AllMCPs.

How Supabase MCP Server works

What alexanderzuev/supabase-mcp-server MCP server does

The alexanderzuev/supabase-mcp-server MCP server exposes Supabase-related operations to MCP clients using the stdio protocol. Its main database function is SQL execution against Supabase PostgreSQL, with configurable read-only and read-write modes. SQL statements are validated at runtime and assigned risk levels, using separate safety tiers for safe, write, and destructive operations.

The server also includes tools for exploring and changing database schemas. Schema changes are versioned automatically. Additional capabilities cover Supabase project administration through the Supabase Management API and user administration through the Supabase Auth Admin SDK.

The repository states that it is no longer actively maintained because Supabase now provides an official MCP server. That maintenance status is an important consideration when choosing the alexanderzuev/supabase-mcp-server MCP server for a new deployment.

How it works

Database access uses asyncpg and a Supabase transaction pooler connection. Local Supabase development defaults to a direct connection at 127.0.0.1:54322, while remote projects use a transaction-pooling endpoint based on the project reference, password, and AWS region. Session pooling is not supported.

The Management API connects to https://api.supabase.com and is available only for remote Supabase projects. Auth Admin requests use the local Supabase URL during local development or the project-specific Supabase URL for remote deployments. These two feature areas are optional and become available when their corresponding credentials are configured.

MCP clients launch the server locally through stdio. The README identifies Cursor, Windsurf, and Cline as compatible clients, along with other clients that support stdio.

Setup and configuration

Python 3.12 or newer is required. The published package can be installed with pipx install supabase-mcp-server or through uv; source installation is also documented. The project requires a QUERY_API_KEY from thequery.dev for all operations.

Required connection settings are SUPABASE_PROJECT_REF, SUPABASE_DB_PASSWORD, SUPABASE_REGION for remote projects, and QUERY_API_KEY. Local-development defaults are provided for the project reference, database password, and region, but remote projects require the actual project values. In particular, SUPABASE_REGION must match the region shown in the Supabase dashboard.

SUPABASE_ACCESS_TOKEN enables Management API access, and SUPABASE_SERVICE_ROLE_KEY enables Auth Admin SDK access. Configuration can come from environment variables, a local .env file when running from source, or a global configuration file under the platform-specific Supabase MCP configuration directory. Installed packages do not read a project-local .env file, so use environment variables or the global file with pipx or uv installations.

Tools and capabilities

  • Execute SQL in read-only or read-write mode.
  • Validate SQL and classify operation risk.
  • Apply safe, write, and destructive SQL safety tiers.
  • Handle transactions over direct and pooled database connections.
  • Explore schemas and version database changes.
  • Manage remote Supabase projects through the Management API.
  • Manage users with Auth Admin SDK methods.
  • Provide pre-built tools intended to help Cursor and Windsurf use MCP.

Limitations and notes

The alexanderzuev/supabase-mcp-server MCP server does not support session pooling. Management API access does not work with local Supabase projects, and Auth Admin or Management API features require separate optional credentials. Remote database connections also depend on the correct Supabase region; a mismatch can produce a tenant or user not found error.

The README explicitly says the project is no longer actively maintained. Supabase's official MCP server is presented as the maintained alternative, so evaluate that option before adopting this repository for long-term use.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Supabase MCP Server

Install Python 3.12 or newer, then run `pipx install supabase-mcp-server` or install it with uv.

It lists Cursor, Windsurf, Cline, and other MCP clients that support stdio.

It requires `SUPABASE_PROJECT_REF`, `SUPABASE_DB_PASSWORD`, `SUPABASE_REGION` for remote projects, and `QUERY_API_KEY`. `SUPABASE_ACCESS_TOKEN` and `SUPABASE_SERVICE_ROLE_KEY` enable optional Management API and Auth Admin features.

Yes. It supports read-only and read-write SQL modes, validates queries at runtime, and assigns risk levels to operations.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSupabase MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/alexanderzuev-supabase-mcp-server?style=directory)](https://allmcps.com/mcp/alexanderzuev-supabase-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/alexanderzuev-supabase-mcp-server"><img src="https://allmcps.com/api/badge/alexanderzuev-supabase-mcp-server?style=directory" alt="Supabase MCP Server on AllMCPs" /></a>