alexander-zuev/supabase-mcp-server

What it solves

This project provides a Model Context Protocol (MCP) server that allows AI-powered IDEs (like Cursor, Windsurf, and Cline) to interact safely with Supabase projects. It eliminates the need for developers to manually switch between their IDE and the Supabase dashboard to run SQL queries, manage database schemas, or handle user authentication.

How it works

The server acts as a bridge between an MCP-compatible client and a Supabase instance. It uses the stdio protocol to communicate with the IDE and connects to Supabase via transaction pooling for database operations, the Supabase Management API for project management, and the Auth Admin SDK for user management. It includes a built-in safety system that categorizes SQL queries into three risk levels (safe, write, and destructive) to prevent accidental data loss.

Who it’s for

Developers using Supabase as their backend who use AI-enhanced IDEs and want to manage their database and users directly through an AI agent.

Highlights

• Three-Tier Safety System: Categorizes SQL operations as safe (read-only), write (data modification), or destructive (schema changes) to prevent accidents.
• IDE Integration: Native compatibility with Cursor, Windsurf, Cline, and Claude Desktop.
• Comprehensive Management: Supports SQL execution, schema versioning, Supabase Management API calls, and Auth Admin SDK methods.
• Risk Assessment: Performs runtime SQL query validation and risk level assessment using the PostgreSQL parser.