Supabase MCP Server Qp4

🚀 Supabase MCP Server

The Supabase MCP (Management Console) Server offers users powerful control over Supabase databases and related services.

🚀 Quick Start

The Supabase MCP Server provides users with comprehensive management capabilities for Supabase databases and associated services.

✨ Features

PostgreSQL Management

• Read-only Queries: Execute SELECT - type read - only SQL queries.
• Read - Write Queries: Perform INSERT, UPDATE, and DELETE operations.
• Destructive Operations: Carry out high - risk database structure modifications such as DROP and TRUNCATE.

Security Management

• Security Modes: There are low - risk, medium - risk, and high - risk levels, corresponding to read - only operations, data modifications, and structure modifications respectively.

Version Control

• Automatic Migration Records: All write and destructive operations on the database will automatically generate migration scripts for subsequent rollback or auditing.
• Unified Security Interface: Achieve consistent risk control for databases, APIs, and SDKs through a single security management interface.

Log Integration

• Supabase Log Connection: Research and support the connection to Supabase database logs to enhance debugging capabilities (if not yet supported).

🔧 Technical Details

Unified Security Mode

Since v0.3.8, all operations are managed using a unified security mode:

• Low - risk Operations: Such as SELECT queries and GET API requests are allowed by default.
• Medium - risk Operations: Such as INSERT, UPDATE, and DELETE operations need to be executed in an insecure mode.
• High - risk Operations: Such as structure modifications like DROP and TRUNCATE or operations that may cause data loss not only require enabling the insecure mode but also double - confirmation.
• Extremely High - risk Operations: Such as deleting a project are completely prohibited.

Confirmation Process

Any high - risk operation (whether it is a PostgreSQL query or an API request) will still be blocked even when the insecure mode is enabled. You must explicitly approve to execute such operations:


📚 Documentation

Database Tools

• execute_postgresql: Used to execute PostgreSQL queries, supporting transaction processing and connection pooling.
• live_dangerously: After enabling the insecure mode, it allows high - risk operations to be executed with confirmation.

API and SDK Interfaces

• Management Console API: Provides programmatic access to Supabase services with integrated security controls.
• Python Native SDK: Supports direct calls to Supabase methods and objects, improving development efficiency.

Version Control System

Since v0.3.8, an automatic version recording function has been introduced. All database changes are tracked in detail, and corresponding migration scripts are generated. In addition, the documentation for tools and services has been significantly enhanced to ensure that users can understand various functions more clearly.

Future Plans

• Log Integration: Research how to connect to Supabase database logs to improve debugging capabilities.
• More Region Support: Expand support for different Supabase regions to enhance the convenience of global applications.

For in - depth technical details or usage guides of the MCP Server, please refer to its [GitHub Discussion Area](https://github.com/alexander - zuev/supabase - mcp - server/discussions/46).