Loading...
This MCP server enables IDEs to interact with Supabase, offering SQL execution, schema management, and access to Supabase Management API and Auth Admin SDK with safety controls.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server enables IDEs to interact with Supabase, offering SQL execution, schema management, and access to Supabase Management API and Auth Admin SDK with safety controls.
This MCP server provides a degree of safety through its tiered system and query validation. However, the ability to perform write operations and access administrative functions introduces risk, especially if the API key and other credentials are not properly secured.
Performance will depend on the complexity of the SQL queries, the size of the database, and the network latency between the MCP server and the Supabase database. Transaction pooling should improve performance compared to direct connections.
Cost considerations include the cost of Supabase resources (database, API calls) and the cost of running the MCP server. Be mindful of API usage to avoid unexpected charges.
brew install postgresql@16{
"mcpServers": {
"supabase": {
"command": "/Users/username/.local/bin/supabase-mcp-server", // update path
"env": {
"QUERY_API_KEY": "your-api-key", // Required - get your API key at thequery.dev
"SUPABASE_PROJECT_REF": "your-project-ref",
"SUPABASE_DB_PASSWORD": "your-db-password",
"SUPABASE_REGION": "us-east-1", // optional, defaults to us-east-1
"SUPABASE_ACCESS_TOKEN": "your-access-token", // optional, for management API
"SUPABASE_SERVICE_ROLE_KEY": "your-service-role-key" // optional, for Auth Admin SDK
}
}
}
}SUPABASE_DB_PASSWORDSUPABASE_ACCESS_TOKENSUPABASE_SERVICE_ROLE_KEYSQL Query ExecutionExecutes SQL queries against the Supabase database.
Allows arbitrary SQL execution, potentially leading to data modification or deletion.
Schema ManagementManages database schema changes, including creating, altering, and dropping tables.
Modifying the database schema can have significant impact on application functionality and data integrity.
Supabase Management API AccessProvides access to the Supabase Management API for managing Supabase projects.
Allows administrative actions on the Supabase project, such as managing users and settings.
Auth Admin SDK MethodsProvides access to Supabase Auth Admin SDK for managing users.
Allows administrative actions on user accounts, such as creating, deleting, and modifying users.
Database Schema VersioningAutomatically versions database schema changes.
Primarily a read operation to track schema changes.
API Key
hybrid
This MCP server provides a degree of safety through its tiered system and query validation. However, the ability to perform write operations and access administrative functions introduces risk, especially if the API key and other credentials are not properly secured.
Autonomy depends on the configured permissions and the safety level of the SQL operations. Destructive operations should be carefully controlled.
Production Tip
Implement robust error handling and monitoring in your MCP client to detect and respond to issues with SQL execution or API calls.
The QUERY_API_KEY is required to use this MCP server and can be obtained for free at thequery.dev.
The server supports transaction pooling connections to Supabase PostgreSQL databases. Session pooling is not supported.
You need to set the SUPABASE_PROJECT_REF, SUPABASE_DB_PASSWORD, and SUPABASE_REGION environment variables.
Yes, the server is configured for local Supabase development by default. You may need to adjust the configuration variables.
Any MCP client that supports the stdio protocol should work. The server has been tested with Cursor, Windsurf, Cline and Claude Desktop.
The project reference is found in your Supabase project URL. The database password was set during project creation or can be found in Project Settings → Database.
The server supports all Supabase regions, including us-west-1, us-east-1, eu-west-1, and ap-southeast-1, among others.
Alexander Zuev
Lead Maintainer