Supabase MCP Server

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.