MCP100 verdict
Connect AI tools to Supabase projects and development workflows.
MCP100 Assessment
Editorial verdict
Connect AI tools to Supabase projects and development workflows.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Working with structured data
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Inspecting one Supabase project's schema, logs, advisors, and docs
- Development environments using project-scoped read-only access
- Teams that understand database and deployment consequences
Not ideal for
- Production database administration by an unattended agent
- Users needing only public Supabase documentation
- Organizations unable to grant Supabase OAuth access to an MCP client
Avoid if
- The server would be left organization-wide rather than project-scoped
- Write-capable SQL, migrations, functions, branches, or storage changes cannot be human-approved
- Production secrets or customer records could be returned to the model
Trade-offs
- Project scoping removes account-level tools but materially reduces blast radius.
- Read-only mode disables mutations but also removes migration, deployment, branch, and storage configuration workflows.
- Branching and some storage capabilities require paid plans; the server is pre-1.0 and may change.
Evidence scope
Evidence
Popularity
2.9k MCP repository stars
No MCP-specific package metric is stored
Stars observed 2026-08-14T18:46:26.000Z · Downloads observation date unavailable
Exact implementation repository metric.
No public package data is mapped to the reviewed MCP.
Maintenance
Publisher activity observed 2026-08-14T06:33:48Z
Current source snapshot
Trust review
Source relationship: First-party MCP
Reviewed 2026-07-24 · Next review 2026-10-24