backup_createLABSCO SUMMARY
Save points for agent edits, deliberately not version control.
It stores full copies rather than diffs and keeps ten versions by default, which is the right shape for "undo the last twenty minutes" and the wrong shape for project history. The project says as much itself — no branching, no merging, no collaboration — so use it before a restructuring and keep Git for everything else.
What it is
A Node server that makes on-demand backups of files and folders for agents and code editors, storing complete copies with the agent's stated reason attached. Tested in Cursor and Windsurf.
What you get
- backup_create for a file, backup_folder_create for a folder with pattern filtering
- backup_list and backup_folder_list for what exists, backup_list_all across everything
- backup_restore and backup_folder_restore to put a version back
- mcp_cancel to stop an operation in progress
- Version history per target, capped by MAX_VERSIONS
- A separate emergency backup location
- The agent's context and reasoning stored with the backup, so a restore point says why it was taken
Requirements
Node, with the server built from the repository with npm. Three environment variables: BACKUP_DIR (./.code_backups), EMERGENCY_BACKUP_DIR (./.code_emergency_backups) and MAX_VERSIONS (10).
Setup effort
Build from source
USE CASES
01
Making a risky edit reversible before you start
Back the file up with the reason attached, so the restore point is identifiable later.
02
Protecting a folder before a restructure
Back up the folder with pattern filtering, so node_modules and build output are not copied along with the source.
03
Undoing an agent's last twenty minutes
List the versions for that file or folder and restore the one from before the change.
04
Finding out what safety net you actually have
List every backup across targets rather than checking one file at a time.
05
Stopping a backup that is taking too long
Cancel the operation in progress instead of waiting it out.
8 tools
Listed in project docs. Your client may show a different list.
backup_listbackup_restorebackup_folder_createbackup_folder_listbackup_folder_restorebackup_list_allmcp_cancelBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
node on PATH
INSTALLATION
Connect your client
MCP Clients
Windsurf
WINDSURF · TERMINAL
git clone https://github.com/hexitex/MCP-Backup-Server.git
cd MCP-Backup-Server
npm install
npm run buildAdd the server to Windsurf with the full path to dist/index.js in that folder
WINDSURF · JSON
{
"mcpServers": {
"backup": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_BACKUP_SERVER>/dist/index.js"
],
"env": {
"BACKUP_DIR": "./.code_backups",
"EMERGENCY_BACKUP_DIR": "./.code_emergency_backups",
"MAX_VERSIONS": "20"
}
}
}
}<YOUR_PATH_TO_MCP_BACKUP_SERVER> is the absolute path of your clone. The README's ./dist/index.js resolves against whatever folder Windsurf starts the server in.
