← Back to directory

Query MCP

Community

Safely manage Supabase through chat.

GitHub source repository ↗

★ 830 Stars Category · Database Very popular

50FMRS · D

Reliability

8/20

Security and permissions

12/20

Maintenance

5/20

Documentation

14/20

Setup experience

11/20

This is a broad Supabase database MCP server with unified safety controls for SQL, migrations, the Management API, Auth Admin, and logs. Its main limitations are support only for Supabase.com-hosted projects and local development, no self-hosting or custom connection strings, and no active maintenance.

Read the FMRS scoring method →

Query MCP is an open-source Supabase MCP server that uses stdio to let compatible clients execute SQL, manage schema changes, call the Supabase Management API, use the Auth Admin SDK, and access logs and analytics. The README states that the project is no longer actively maintained because Supabase has released an official MCP server.

Tools

get_schemas

Lists database schemas with sizes and table counts.

get_tables

Lists tables, foreign tables, and views with metadata.

get_table_schema

Returns detailed table structure, including columns, keys, and relationships.

execute_postgresql

Executes PostgreSQL statements with risk assessment.

confirm_destructive_operation

Executes a high-risk database operation after explicit confirmation.

retrieve_migrations

Retrieves migration records with filtering and pagination.

live_dangerously

Toggles between safe and unsafe modes.

send_management_api_request

Sends a request to the Supabase Management API and injects the project reference.

get_management_api_spec

Returns the Management API specification with safety information, parameter requirements, and response formats.

get_management_api_safety_rules

Returns safety rules with human-readable explanations.

get_auth_admin_methods_spec

Retrieves documentation for available Supabase Auth Admin methods.

call_auth_admin_method

Invokes a Supabase Auth Admin method with parameter handling.

retrieve_logs

Accesses logs and analytics data from Supabase services.

Setup

Python 3.12+ is required. Install with pipx install supabase-mcp-server or uv pip install supabase-mcp-server, or install from the repository root in editable mode. Configure QUERY_API_KEY, SUPABASE_PROJECT_REF, and SUPABASE_DB_PASSWORD; remote projects should also specify the correct SUPABASE_REGION. Management API access requires SUPABASE_ACCESS_TOKEN, while Auth Admin access requires SUPABASE_SERVICE_ROLE_KEY. Add the server command to an MCP client configuration; Claude Desktop, Cline, and similar clients generally require the executable's absolute path.

claude_desktop_config.json

{"mcpServers":{"supabase":{"command":"/full/path/to/supabase-mcp-server","env":{"QUERY_API_KEY":"your-api-key","SUPABASE_PROJECT_REF":"your-project-ref","SUPABASE_DB_PASSWORD":"your-db-password","SUPABASE_REGION":"us-east-1","SUPABASE_ACCESS_TOKEN":"your-access-token","SUPABASE_SERVICE_ROLE_KEY":"your-service-role-key"}}}}

Generate and validate client config

Fit and risk

Best for

Supabase developers using Cursor, Windsurf, Cline, or Claude Desktop.
Teams that want SQL, project management, authentication administration, and logs in one interface.
Development environments using local Supabase or Supabase.com-hosted projects.

Not for

Users who need self-hosted Supabase support.
Users who need custom connection strings or Session Pooling.
Production teams that require ongoing maintenance, official support, or the latest features.
Local-only Supabase users who need Management API or Auth Admin features.

Required permissions

Requires a database project reference and database password.
All operations require a QUERY_API_KEY from thequery.dev.
Management API operations require a Supabase personal access token.
Auth Admin operations require a Supabase service role key.
Database connections use transaction pooling; remote projects require the correct Supabase region.

Risks and side effects

Safe mode permits only low-risk read-only operations by default.
Write operations require unsafe mode, and high-risk operations also require explicit confirmation.
Extreme-risk operations, such as deleting a project, are blocked.
Automatically generated migrations do not eliminate the risk of incorrect SQL or data loss when using high-privilege credentials.
The service role key and database password are highly sensitive credentials.
The project is no longer actively maintained, and the README points users to Supabase's official MCP server.

Troubleshooting

Run supabase-mcp-server directly to verify installation and configuration.
If tools are missing or spawn ENOENT occurs, use the executable's full absolute path.
Check environment variables or the global configuration file for the correct project reference, database password, and API key.
For a Tenant or user not found error on a remote project, verify SUPABASE_REGION.
Inspect ~/.local/share/supabase-mcp/mcp_server.log on macOS/Linux or the corresponding user directory on Windows.
Confirm that the remote project uses transaction pooling rather than Session Pooling.

Use cases

Querying and modifying Supabase PostgreSQL through natural language.

Inspecting schemas, table structures, and automatically versioned migrations.

Managing remote Supabase projects and accessing service logs.

Creating, listing, updating, or deleting test users and generating authentication links.

Supported clients

CursorFull support

WindsurfFull support

ClineFull support

Claude DesktopFull support

Related MCP servers

Compare with other MCP servers