Supabase MCP Branching Readiness Checker

Paste redacted Supabase MCP tool notes or error text and check whether project-scoped branching can support a safe migration workflow. The narrow risk: if create_branch needs a cost-confirmation tool that is not available in project scope, an agent may fall back to production migrations.

Review order

1
Confirm project scopeProject scoping limits access to one project, but account-management tools are disabled.
2
Check branching prerequisitescreate_branch should not depend on unavailable confirm_cost evidence.
3
Protect migrationsStaging branch failure should block the agent, not push apply_migration straight to production.

Project label Paste redacted MCP tool notes, tools/list excerpt, or error text

Use redacted text only. Do not paste access tokens, project secrets, private connection strings, real user data, customer records, private screenshots, payment data, full names, private handles, credential values, or full transaction identifiers. This page runs locally in the browser and does not use network requests, browser storage, or a backend.

Ready.

Branching findings

Acceptance checks before agent-managed migrations

list_branches works in the same project-scoped connection the agent will use.
create_branch is callable without an account-scoped prerequisite, or the scoped cost-confirmation path is visible and tested.
apply_migration runs only against a development branch until the branch is verified.
merge_branch has a manual approval gate and a rollback note before production changes.
tools/list does not advertise a happy-path staging workflow that cannot actually be called in the configured scope.

Check paid report scope Review tools/list Read sample Supabase report

Need a second pass?

The fixed-scope report can review one redacted Supabase MCP branching or grants/RLS packet: likely blocker, project-scope mismatch, migration safety gate, and concrete regression checks. The sample Supabase report is fictional and shows the report shape before checkout.

Buy $25 Supabase report Read sample report

Source-backed problem set

Open Supabase MCP issue Project-scoped branching report where create_branch is blocked by unavailable cost-confirmation tools and list_branches cannot resolve project reference. Supabase MCP docs Official docs describe project scoping, feature groups, account-management tools, and branching support. Related tools/list safety issue Open report about read-only mode still exposing mutating tools in tools/list.