Supabase MCP Server: Manage Supabase from Claude

The Supabase MCP server is Supabase’s official Model Context Protocol server. It connects Claude to your Supabase projects so it can manage tables, run queries, fetch configuration, and look up Supabase docs. The hosted endpoint uses OAuth, so your MCP client prompts you to log in to Supabase during setup.

Who it is for

Developers building on Supabase who want Claude to design schemas, write migrations, debug RLS policies or inspect data without switching to the dashboard.

Install

Read Supabase’s security best practices first. The README’s client config:

{
  "mcpServers": {
    "supabase": {
      "type": "http",
      "url": "https://mcp.supabase.com/mcp"
    }
  }
}

In Claude Code, the equivalent is:

claude mcp add --transport http supabase https://mcp.supabase.com/mcp

Scope it down with URL parameters, for example https://mcp.supabase.com/mcp?project_ref=<project-ref>&read_only=true&features=database,docs. The dashboard’s MCP connection tab can generate this URL for you. A Supabase plugin is also listed in Anthropic’s marketplace.

Use cases

• Design a schema and generate a migration from a feature description.
• Debug a failing Row Level Security policy with real table definitions.
• Explore data read-only while investigating a bug.
• Look up current Supabase docs while implementing auth or storage.

Pros

• Official, hosted, OAuth-based; nothing to run locally.
• Fine-grained scoping by project, feature group and read-only flag.
• Also usable from Vercel’s AI SDK via the exported tool schemas.

Cons and caveats

• Write access to a production database is high risk; prompt injection from data rows is a real concern.
• Local CLI and self-hosted modes expose fewer tools and no OAuth 2.1.
• Query results add tokens; ask for aggregates instead of full tables.

Links

• Repo: supabase/mcp
• Docs: supabase.com/mcp
• Related: Supabase agent skills, DBHub, best MCP servers