Is there a way to rollback changes made by DesktopCommanderMCP?
I'm using DesktopCommanderMCP with Claude and the agent modified several files in my project. There seems to be no built-in undo or version history for MCP changes, so the only way back is manually copy-pasting the old files. Is there a workaround to revert to a known-good version without doing that by hand?
Originally asked on GitHub: https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/22
3 answers
Still open: as of the thread (opened 2025-03-24), DesktopCommanderMCP has no built-in version tracking or rollback feature. A project collaborator agreed that rollback would be nice, but described it as more of a personal workflow problem than a bug in the tool. No fix or version number was mentioned.
The practical workaround suggested in the thread is to combine DesktopCommanderMCP with the GitHub MCP server. The commenter's advice: install GitHub MCP alongside DesktopCommanderMCP, then ask Claude how git branches, commits, pulls, and pushes can help you recover if you mess up. Before trying new functionality, create a new branch with a suitable name and experiment on that branch. If the changes break everything, you can pull your last working codebase from the previous branch instead of manually reverting each file.
This approach lets you keep talking to the model while still having a clean recovery point, and it uses tools Claude can already drive through the MCP servers. The thread did not report anyone testing this workflow end-to-end, so treat it as a suggested approach rather than a confirmed fix. No security note is needed: the concern here is recovery from agent-made changes, not secret handling.
Did this work for you?What @fjordnode tried on GitHub (Outcome unclear)
A commenter suggested installing GitHub MCP alongside DesktopCommanderMCP and asking Claude to use git; the workflow is to make a new branch before experimenting, then pull the last working codebase to revert if needed.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
The reporter said the only way to undo MCP-created changes was manually copy-pasting files, because no built-in version tracking or rollback exists in the tool.
Source: https://github.com/wonderwhy-er/DesktopCommanderMCP/issues/22 (opens external site)
Did this work for you?
Related questions
- DesktopCommanderMCP: 'MCP error -32001: Request timed out' on startup with Claude Desktop
- DesktopCommanderMCP fails to attach under nvm: require() of ES modules is not supported
- search_code errors in DesktopCommanderMCP on Claude Desktop, then falls back to read_file/search_files
- DesktopCommanderMCP polls running processes in a loop and hits Claude limits — how to make it wait?
- DesktopCommanderMCP: how to read large HTML pages when results cap at 1048576 characters?