DEV.co
MCP Servers · alexander-zuev

supabase-mcp-server

Supabase MCP Server is a Python-based Model Context Protocol server that enables AI assistants and IDEs to manage Supabase databases through a chat interface. It supports SQL query execution with safety controls, schema migrations, and management API integration. The project is no longer actively maintained as the official Supabase MCP server is now recommended.

Source: GitHub — github.com/alexander-zuev/supabase-mcp-server
828
GitHub stars
105
Forks
Python
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryalexander-zuev/supabase-mcp-server
Owneralexander-zuev
Primary languagePython
LicenseApache-2.0 — OSI-approved
Stars828
Forks105
Open issues3
Latest releasev0.4 (2025-04-03)
Last updated2026-05-08
Sourcehttps://github.com/alexander-zuev/supabase-mcp-server

What supabase-mcp-server is

A stdio-compatible MCP server written in Python 3.12+ that provides asyncpg-based database connections to Supabase PostgreSQL instances, with three-tier SQL safety validation (safe/write/destructive), transaction handling, automatic migration versioning, and integration with Supabase Management API and Auth Admin SDK. Requires a free API key from thequery.dev.

Quickstart

Get the supabase-mcp-server source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/alexander-zuev/supabase-mcp-server.gitcd supabase-mcp-server# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Database Management via Chat Interface

Execute SQL queries, manage schema changes, and handle migrations through Cursor, Windsurf, or Cline without leaving your IDE—useful for rapid prototyping and exploratory development.

Supabase Project Administration

Automate user management via Auth Admin SDK and interact with Supabase Management API for project-level operations through natural language commands.

Local Development Workflows

Streamline local Supabase instance setup and operations with pre-configured defaults (127.0.0.1:54322) and simplified PostgreSQL integration.

Implementation considerations

  • Requires Python 3.12+ and a package manager (pipx or uv recommended); installation via pipx is preferred for environment isolation.
  • Configuration via environment variables or global `.env` file; local `.env` files not detected when installed via package manager—must set via client or global config.
  • Mandatory API key registration at thequery.dev even for local development; no offline-first option available.
  • Database connection uses transaction pooling (not session pooling); remote projects require correct SUPABASE_REGION configuration or will fail with 'Tenant or user not found' error.
  • Three-tier SQL safety system (safe/write/destructive) with runtime validation; operators should understand safety implications for their query patterns.

When to avoid it — and what to weigh

  • Seeking Active Maintenance — The author explicitly states this project is no longer actively maintained in favor of the official Supabase MCP server, which will receive future feature additions.
  • Production Safety-Critical Systems — While the server includes safety controls (query validation, risk assessment), the lack of active maintenance and community suggests it should not be deployed as the sole access layer for critical production databases.
  • Offline or Air-Gapped Environments — Requires a free API key from thequery.dev, making it unsuitable for fully offline or air-gapped deployments.
  • Teams Without Python Expertise — Installation and configuration require Python 3.12+, package manager familiarity, and environment variable management—not ideal for non-technical teams.

License & commercial use

Apache License 2.0 (Apache-2.0). A permissive OSI-approved open-source license allowing commercial use, modification, and distribution with attribution and liability disclaimer.

Apache-2.0 is a permissive license compatible with commercial use. However, the project is no longer actively maintained; commercial deployments should evaluate the official Supabase MCP server or fork this repository and assume maintenance responsibility. No warranty or support from the original author should be assumed.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceStale
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

The server implements runtime SQL query validation with risk level assessment and a three-tier safety system (safe/write/destructive); review the safety implementation to understand threat model alignment. Credentials (SUPABASE_DB_PASSWORD, SUPABASE_ACCESS_TOKEN, SUPABASE_SERVICE_ROLE_KEY, QUERY_API_KEY) must be stored securely via environment or config files; avoid hardcoding. The server does not itself manage encryption in transit or at rest—security depends on Supabase infrastructure and the MCP client. Audit and rate-limiting are not mentioned; evaluate operational requirements. No security audit or third-party assessment is documented.

Alternatives to consider

Official Supabase MCP Server (supabase-community/supabase-mcp)

Officially maintained by Supabase, feature-parity with this project, and committed to ongoing development. Recommended by this project's author as the successor.

Supabase Python SDK with Direct Integration

Lower-level library-based approach; more control but requires custom MCP wrapper or IDE plugin development; suitable for teams with Python expertise and integration needs.

Anthropic Cline with Native Database Tools

If using Cline as your MCP client, consider native database tool integrations that may not require a separate MCP server for simpler query workflows.

Software development agency

Build on supabase-mcp-server with DEV.co software developers

This project is no longer maintained. Use the official Supabase MCP server (supabase-community/supabase-mcp) for ongoing support, active maintenance, and future features. If you require a custom fork or specialized integration, consult with a development team.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

supabase-mcp-server FAQ

Is this project still maintained?
No. The author explicitly states it is no longer actively maintained in favor of the official Supabase MCP server. Use the official server for ongoing support.
Do I need PostgreSQL installed locally?
Only if running a local Supabase instance. The MCP server itself uses asyncpg (pure Python) and does not require PostgreSQL development libraries.
What is the thequery.dev API key requirement?
Since v0.4, a free API key from thequery.dev is required for all operations. This enables query validation and safety controls; registration is mandatory.
Why do remote Supabase projects fail with 'Tenant or user not found'?
Almost certainly due to incorrect SUPABASE_REGION setting. The region must match your project's actual region in the Supabase dashboard; verify in Project Settings.

Custom software development services

From first prototype to production, DEV.co delivers software development services around tools like supabase-mcp-server. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across mcp servers and beyond.

Need Active Supabase MCP Integration?

This project is no longer maintained. Use the official Supabase MCP server (supabase-community/supabase-mcp) for ongoing support, active maintenance, and future features. If you require a custom fork or specialized integration, consult with a development team.