Supabase MCP Server

What it does

The Supabase MCP Server connects Model Context Protocol clients, such as AI coding assistants, to your Supabase projects. The client sends natural-language requests and tool calls, and the server returns results from the project, including table lists, SQL query output, migration status, logs, security and performance advisors, project URLs, generated TypeScript types, and documentation search results.

Developers use it to let an assistant inspect a database, run SQL, apply migrations, query logs, and deploy Edge Functions from within an IDE. Tools are organized into feature groups such as Database, Debugging, Development, Edge Functions, Account management, Docs, Branching, and Storage. The server can be scoped to one project and set to read-only, and elicitation prompts can pause actions like cost confirmation or destructive SQL where the client supports them.

It suits developers who already use an MCP-capable client and a Supabase account. Setup adds a remote HTTP server entry to the client, followed by browser sign-in to grant access to an organization. Connecting an LLM to projects carries security risks, elicitations are guardrails rather than guarantees, Branching requires a paid plan, and Storage tools are disabled by default.

What it can do

• Lists tables, extensions, and migrations, and applies migrations
• Executes SQL queries, with destructive-SQL confirmation where the client supports forms
• Queries project logs and retrieves security and performance advisors
• Deploys and manages Edge Functions and their secrets
• Generates TypeScript types from the database schema
• Searches Supabase documentation

Works with

• Claude Code
• Cursor

Before you choose

• Connecting an LLM to Supabase projects carries security risks; read the security best practices before running the server, and keep read-only mode and project scoping in place where possible.
• Elicitations are a guardrail, not a guarantee of human review, and some clients answer them automatically; they do not replace your client's own tool approval.
• Branching requires a paid plan; Storage tools are disabled by default.

Listed under

• Coding
• MCP and agent tools
• AI coding agents
• AI coding assistants
• Backend
• Database
• Developer tools
• Mcp

Get started

Use the Claude Code command or the .mcp.json entry, then authenticate through the browser.

1. Choose your Supabase platform, project, and MCP client on the MCP guide, and copy the server URL with the selected features.
2. Add the server to your client, for example with 'claude mcp add --scope project --transport http supabase' or the .mcp.json entry, then authenticate via 'claude /mcp' or the client's login prompt.
3. Confirm the server is connected in your client's tool settings, then ask it a question about your database, such as listing tables.

Branching requires a paid plan, and cost confirmation applies when creating projects and branches. Check your Supabase organization for current rates.

We couldn’t find published prices for Supabase MCP Server.

Sources for this overview

Product pages, documentation, and pricing checked 29 Oct 2026. Each source supports part of the overview; availability and prices can change.

• Supabase MCP Server | Supabase Docs ↗supabase.com
• Supabase Docs ↗supabase.com

Company website

supabase.com: product, pricing and policy pages

Hacker News

Launch posts and discussion

YC directory mirror

Batch and company name

Social accounts

Accounts the company links, and its posts on X

Human review

Checked by a person

knowledge_base

manual_review

Last checked 29 Oct 2026. Every field keeps its source and date; unknown means we couldn’t confirm it.