Change the schema or data with a way back
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
The change runs on a branch, staging or a dry run first, the person sees the exact DDL or DELETE before it touches the main branch, the migration is recorded, and production is changed only by the approved step.
How agents ask for it: add a column and migrate the data
, apply this migration to staging
, restore yesterday's snapshot
, run the migration on a branch first
Does the job, with a limit 3
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Neon MCP Server BB Neon, LLC (subsidiary of Databricks, Inc.) | prepare_database_migration applies changes on a temporary branch and complete_database_migration applies them separately, but #444 (open) reports restore_snapshot with only snapshot_id swapping production twice, against the README's description. source |
| PlanetScale MCP Server BB PlanetScale, Inc. | execute_write_query takes a branch and carries destructiveHint, but DELETE and DDL approval is a confirm_destructive argument the model sets after the tool asks it to check with the user, not a prompt the client shows. source |
| Supabase API + MCP BB Supabase Pte. Ltd. | Experimental branching (create, merge, reset, rebase), tracked apply_migration and SQL elicitation on destructive statements fit, but #472 shows the confirmation failing so a reviewed staging migration could not run, and the docs call elicitation a guardrail. source |
Doesn't do this job 14
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| Mirage (AgentVFS) B Strukto.AI | The Postgres VFS is read-only; no migration, branch or dry-run path. source |
| ClickHouse MCP Server BB ClickHouse, Inc. | No branch or dry-run apply; CLICKHOUSE_ALLOW_DROP is an operator flag, not a confirmation the person sees, and the README calls it best-effort. #24 shows Claude going round read-only with curl. source |
| CoinMarketCap x402 API BB CoinMarketCap | No schema or write operations on a database. source |
| DBHub BB Bytebase | No branch, dry-run apply or migration record; with readonly off, execute_sql runs DDL and DELETE directly with no confirmation step. source |
| Filesystem (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | No database or migration tools; edit_file dryRun previews file edits only. source |
| MCP Toolbox for Databases A Google LLC | No branch or migration record; execute_sql runs DDL directly and its docs say it is for human-in-the-loop developer use. BigQuery dry-run validates SELECTs only. source |
| Memory (MCP reference server) B Model Context Protocol, a Series of LF Projects, LLC | No schema changes or branches. |
| MongoDB MCP Server A MongoDB, Inc. | No branch, dry run or migration record. Elicitation confirms drop and delete-many by default, but the README says the tool runs without confirmation when the client lacks elicitation. source |
| Nansen x402 API B Nansen | No schema or write operations on a database. source |
| ObsessionDB F Kellerkind UG (haftungsbeschränkt) | No branch, dry-run or migration tool in the twelve MCP tools; per-agent branches are marked early access on the home page only. source |
| Postgres MCP Pro F Crystal Corp. | No branch, dry-run apply or confirmation; unrestricted mode executes DDL directly and restricted mode blocks writes. source |
| Redis MCP C Redis Ltd. | No schema changes, branches or dry runs; deletes run without confirmation. source |
| ReqRes MCP server D ReqRes | No schema migrations, branches or dry runs. source |
| Snowflake-managed MCP server C Snowflake Inc. | No branch, dry-run or migration tools; SQL execution runs what it is given under the role. source |
What stops agents finishing
- confirmation step fails in the client so an approved write cannot run
- destructive defaults (restore onto source branch, finalise true)
- agent routes round a read-only server through another tool
Around it
Before: data.schema-check. After: code.ticket-to-pr.
Where this comes from
Weight 14 of 100 in Databases & files: 9 of 52 accounts, most of them failures (deleted or swapped production, a confirmation flow that breaks, writes blocked by read-only); weighted for the cost of getting it wrong
The same as data: /api/v1/use-cases/data.safe-migration.json, or the MCP tool get_use_case with id data.safe-migration. Other jobs in this category: /api/v1/niches?category=data.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.