@supabase/mcp-server-supabase

What it does

The Supabase MCP server exposes your Supabase project resources to AI assistants like Claude, Cursor, and Windsurf. It supports database queries via SQL execution, schema inspection, table and policy management, edge function deployment, storage bucket operations, and project-level tasks like branching and migrations. Configuration uses URL query parameters to enable optional read-only mode and project scoping, with a features parameter to customize which tool groups the LLM can access.

Who it's for

Backend and full-stack engineers building on Supabase who want their AI assistant to interact directly with live database state, execute migrations, deploy functions, and troubleshoot schema issues without leaving the editor or IDE.

Common use cases

• Query live Postgres data within Claude to provide context for debugging or code generation
• Execute schema migrations and table modifications through the AI assistant
• Deploy and manage Supabase edge functions from within Cursor or Windsurf
• Perform read-only database introspection to understand schema structure for new feature development
• Troubleshoot data integrity and access control policies interactively

Setup pitfalls

• Two secrets were detected in the codebase during scanning; rotate any exposed credentials immediately if accessed by untrusted parties
• Read-only mode is not enabled by default—explicitly set read_only=true in the server URL to restrict the LLM to read operations only
• Without the project_ref query parameter, the server has access to all projects in your organization; scoping to a specific project is recommended
• Self-hosted and CLI deployments offer only a limited tool subset and do not support OAuth 2.1