Labsco
MCP SERVER

Backup

by hexitex

Take a snapshot before a risky edit and put it back if the agent goes wrong.

Local Filesystem Access
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, built from the repository with npm, or installed through Smithery. Three environment variables: BACKUP_DIR (./.code_backups), EMERGENCY_BACKUP_DIR (./.code_emergency_backups) and MAX_VERSIONS (10).

Setup effort

One command — npx -y @smithery/cli install @hexitex/MCP-Backup-Server --client claude