[jasdeepkhalsa]

The MCP tools now use the CLI's vocabulary, and each tool's annotations tell the truth about it.

Was	Now	Annotation
scan_drift	diff: every difference, plus the plan sync would run	Read-only
apply_fixes	sync: runs that plan; prove: true rehearses it first	Destructive
(none)	list_environments: environment names, never credentials	Read-only
create_migration	Now writes exactly what migrate create writes	Writes files

Why two tools rather than one with a flag: clients decide what to run unattended from readOnlyHint and destructiveHint, which apply to a whole tool. A tool that both plans and writes has to be marked destructive, so a client asks before every plan. Otherwise it's marked read-only while able to write.

• diff: writes nothing. Returns the findings, the drift score and plan: the statements sync would run, in order, and what it holds back and why. apply_fixes previewed by default but listed its preview under applied.
• sync: takes the same arguments as diff, so the plan an agent shows is the plan that runs. Fixes that drop tables or columns are still held back unless allowDestructive is set. prove rehearses on a throwaway copy of the target and refuses to write if the copy wouldn't match the source.
• Shared proof: the proof step moves out of the diff command into prove-gate, so diff --apply --prove and sync decide the same way. The CLI's output is unchanged.
• list_environments: for clients that show tools but not resources, which had no way to learn environment names short of reading the config file.
• create_migration: used to diff two snapshots of one environment. It now writes the source-to-target migration migrate create writes, with the grants on what it creates and a DOWN. Building the file moves into migration-file, shared by both.
• Finding descriptions: schema and data findings now say in words what differs and what the fix does, instead of "difference detected by @dbdiff/cli".

Breaking: the tool names change. This is pre-1.0, so there are no aliases; two names for each action would only confuse agents.

Tested:

• Unit tests, build and lint all pass, with new tests showing that diff and sync share arguments and that sync defaults hold back drops and don't prove.
• Run live over stdio against two real databases:
  • list_environments returns no connection strings.
  • diff returns a 4-statement plan.
  • sync with prove: true converges and applies all 4; a second diff comes back clean.
  • create_migration reports nothing left to write.
  • With a client pg_dump too old for the server, sync with prove refuses and writes nothing.

🤖 Generated with Claude Code