Rollback deployed site to previous version
The live site URL now points to a previously deployed version, effectively reverting recent changes.
How it works
Changes data in your accountsOperations and infrastructure
The agent first retrieves the list of previous deploys using 'aft_deploys', requiring the 'edit_token' from the site's state. It then identifies the target 'deploy_id' to roll back to. Finally, it calls 'aft_rollback' with the target ID and the 'edit_token' to point the live slug at that prior version. This is useful for undoing broken deployments.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Rollback deployed site to previous version
List the previous deploys for the site with edit_token 'abc123' and rollback to the second most recent version.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
aft_rollback Point the live slug at a prior deploy_id . Same URL.MCP for agents — aft.page