Rollbackplan runs on your own machine — the client starts it, so there is no endpoint to ping. 289 installs a week from npm. Last commit 2 Nov 2026.
Plan a release rollback: flags first, then env changes, then migrations in reverse order.
Nothing serious here today
Today is the operative word: we check Rollbackplan every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add rollbackplan -- npx -y @reneturcios/rollbackplan{
"mcpServers": {
"rollbackplan": {
"command": "npx",
"args": [
"-y",
"@reneturcios/rollbackplan"
]
}
}
}[mcp_servers.rollbackplan]
command = "npx"
args = ["-y", "@reneturcios/rollbackplan"]{
"mcpServers": {
"rollbackplan": {
"command": "npx",
"args": [
"-y",
"@reneturcios/rollbackplan"
]
}
}
}{
"servers": {
"rollbackplan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/rollbackplan"
]
}
}
}Alternatives to Rollbackplan
same job, measured the same wayPlan a safe file or export rename: reference graph, edit order, and risk flags first.
Send AI-made document changes for human review, then read the decisions back.
AI model releases, price changes and deprecations in one feed: chat, embedding, speech, video.
Plan an event in chat: venue ideas, RSVP deadline and past events, then email invites and RSVPs.
AI model releases, price changes, comparisons and cost estimates in one normalised feed.
Audit a landlord's CAM reconciliation against the lease. Finds overcharges with clause citations.
Pre-release gate: block a release when git tag, package version, and changelog entry disagree.
Search Console in your AI IDE: the plan, stored history, and a measured record of every change.
Rollbackplan — questions
Answers built from our own checks of this server.