Database inspection
List tables, extensions, migrations, and execute SQL; read-only mode changes the query user.
Documentation ↗MCP server / databases / source-linked
Supabase MCP
Supabase MCP is a hosted, OAuth-authenticated bridge to a Supabase organization or project. It exposes database, documentation, debugging, development, functions, branching, account, and optional storage groups. The setup UI supports project scoping, read-only mode, and feature-group selection, which are meaningful safety controls for production databases.
Before you choose.
Identify the implementation and the job it supports.
Supabase MCP is a hosted, OAuth-authenticated bridge to a Supabase organization or project. It exposes database, documentation, debugging, development, functions, branching, account, and optional storage groups. The setup UI supports project scoping, read-only mode, and feature-group selection, which are meaningful safety controls for production databases.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Streamable HTTP
- Authentication
- OAuth 2.1/dynamic client registration; a scoped PAT can be used for CI clients that cannot open a browser.
Choose project, read-only flag, and feature groups; add https://mcp.supabase.com/mcp to the client; complete browser authentication. For Claude Code use the official claude mcp add command.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
claude mcp add --scope project --transport http supabase "https://mcp.supabase.com/mcp?project_ref=PROJECT_REF&read_only=true&features=database,docs"What it actually exposes.
Concrete capabilities with maintainer sources.
Debugging and advisors
Query project logs and request security/performance advisors.
Documentation ↗Development operations
Generate TypeScript types, inspect/deploy Edge Functions, and search Supabase docs.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Signal: permissions and project context
Multiple users reported the same privilege error; one reply says renaming the MCP server in mcp.json fixed it for Cursor, while another points to confusion when multiple projects are available.
“Your account does not have the necessary privileges to access this endpoint”Open community source ↗
Signal: oauth registration recovery
A hosted MCP OAuth client with a stale dynamic-registration ID could not recover: every re-authentication repeated a raw 422 JSON error until the cached registration was replaced.
“Unrecognized client_id”Open community source ↗
Signal: high utility high blast radius
A user reports strong productivity gains for schema changes, RLS policies and index work from Cursor, while replies warn that broad write access can enable data exfiltration.
“Create and update tables ... Fix RLS policies ... Optimize and update indexes”Open community source ↗
Signal: environment scope gap
The issue says project-level MCP scope does not map cleanly to branch environments, making it difficult to prevent an agent from reaching production while allowing development and staging work.
“least-privilege access difficult”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Safe schema triage
Suggested evaluation, not an observed test result.
- Connect to one project with read_only=true and only database,docs,debugging groups.
- Ask for a schema inventory and advisor findings with source table names.
- Have a human review proposed SQL before any migration or function deployment.
What to inspect: A scoped diagnostic report with no unreviewed production write. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Supabase warns that connecting an LLM to production data creates prompt-injection and data-exposure risk; scope a project and enable read-only where possible.
Boundary reference ↗Branching tools require a paid plan and storage tools are disabled by default.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A scoped diagnostic report with no unreviewed production write. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Neon MCP | Choose for Neon-specific branch, endpoint, and Postgres lifecycle operations. | Neon has a narrower vendor surface but offers explicit read/write scopes and project categories. Documentation ↗ |
| Google Gen AI Toolbox | Choose for a self-hosted multi-database or custom restricted-tool layer. | Requires managing the server and database credentials yourself. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Do I need a PAT?
Interactive clients use browser OAuth; a scoped PAT is documented for CI or clients without dynamic registration.
Documentation ↗
Can I limit access?
Use project_ref, read_only=true, and features parameters to reduce project and tool-group scope.
Documentation ↗
Source trail.
Maintainer documentation used in this record.