supabase

This Supabase MCP Server provides a comprehensive, programmatic interface to your Supabase PostgreSQL database. It exposes a broad set of database management tools via MCP compatible commands, enabling tasks such as listing and managing tables, columns, indexes, constraints, records, functions, triggers, policies, roles, buckets, and more. You can interact with these tools through Cursor’s MCP or Codeium’s Cascade, allowing natural-language or scripted control over your database. To use it, deploy the server and configure Cursor or Cascade to point at the built server command, then invoke tools like list_tables, create_table, or fetch_records as part of your workflow. The server is designed for administrators who need deep, programmatic access to database operations without directly writing SQL for every task.

Prerequisites:

• Node.js >= 16.x
• npm >= 8.x
• Access to a Supabase project (Project ID, database password, and connection string)

Step-by-step:

1. Clone the repository:

git clone https://github.com/Quegenx/supabase-mcp-server.git
cd supabase-mcp-server

2. Install dependencies:

npm install

3. Build the project:

npm run build

4. Run or integrate with MCP clients:

• For Cursor: configure the MCP server in Cursor settings with a command like:

node /path/to/dist/index.js postgresql://postgres.[PROJECT-ID]:[PASSWORD]@aws-0-eu-central-1.pooler.supabase.com:5432/postgres

• For Windsurf/Cascade: point to the same built dist path and supply the connection string in mcp_config.json as shown in the README.

Notes:

• Keep your database credentials secure and avoid committing them to version control.
• Ensure the connection string uses the correct project details and password.

Tips and caveats:

• This MCP server exposes a large surface area of database operations; consider using read-only or restricted tool sets in production if needed.
• For Cascade integration, tools are available but prompts and resources are not; tool calls consume credits regardless of outcome.
• Ensure environment compatibility for stdio-based transports; if you need environment variables, consider wrapping the server with a script that injects them at startup.
• Regularly update dependencies and rebuild to get the latest tool capabilities and security updates.