MCP undo

Every MCP change is recorded as a batch that can be taken back, with a check that nothing changed since.

Each write through MCP returns an undo id (v2) or a batch id (v1). Undo takes back that whole change, last part first. If the site changed meanwhile, the undo stops and says what is left instead of overwriting newer work.

How it works

  • Studio History uses the same mechanism.
  • Not undoable: app installs, restore of a published backup.

When to use it

  • Revert an agent's bad edit safely

Limitations

  • Undo ids work once
  • Stops when later changes touch the same things

Availability

  • Works in MCP and AI Studio.
  • Included in every plan.

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.