What is Mcp Backup Server

MCP-Backup-Server is a specialized Model Context Protocol (MCP) server that provides file backup and restoration capabilities specifically designed for AI agents and code editing tools.

Use cases

Use cases include creating backups before risky code changes, restructuring project folders, managing multiple related updates, resuming significant work, and ensuring safety before restoration operations.

How to use

To use MCP-Backup-Server, install the dependencies using ‘npm install’, build the TypeScript files with ‘npm run build’, and start the server with ‘npm start’. Configure the server settings in your editor as per the provided examples.

Key features

Key features include preserving agent context and reasoning, creating targeted backups, supporting file and folder operations, maintaining version history, providing restore safety, and allowing operation cancellation.

Where to use

MCP-Backup-Server is ideal for use in software development environments, particularly where AI agents are involved in code editing and management, such as in Cursor and Windsurf editors.

MCP Backup Server

A specialized MCP server that provides backup and restoration capabilities for AI agents and code editing tools. Tested in both Cursor and Windsurf editors.

Repository: https://github.com/hexitex/MCP-Backup-Server

Why Use This (Not Git)

This system serves a different purpose than Git:

Pros:

• Creates instant, targeted backups with agent context
• Simpler than Git for single-operation safety
• Preserves thought process and intent in backups
• No commit messages or branching required
• Better for AI agents making critical changes
• Works without repository initialization
• Faster for emergency “save points” during edits

Cons:

• Not for long-term version tracking
• Limited collaboration features
• No merging or conflict resolution
• No distributed backup capabilities
• Not a replacement for proper version control
• Stores complete file copies rather than diffs

When to use: Before risky edits, folder restructuring, or when you need quick safety backups with context.

When to use Git instead: For proper version history, collaboration, and project management.

Features

• Preserves agent context and reasoning
• Creates targeted, minimal backups
• Supports file and folder operations
• Maintains version history
• Provides restore safety
• Uses pattern filtering
• Tracks operations
• Allows cancellation

Setup

Installing via Smithery

To install Backup Server for Claude Desktop automatically via Smithery:

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

Installing Manually

# Install dependencies
npm install

# Build TypeScript files
npm run build

# Start the backup server
npm start

Config

Env:

• BACKUP_DIR: Backup directory (./.code_backups)
• EMERGENCY_BACKUP_DIR: Emergency backups (./.code_emergency_backups)
• MAX_VERSIONS: Version limit (10)

Configure in editor:

Windsurf MCP config:

{
  "mcpServers": {
    "backup": {
      "command": "node",
      "args": [
        "./dist/index.js"
      ],
      "env": {
        "BACKUP_DIR": "./.code_backups",
        "EMERGENCY_BACKUP_DIR": "./.code_emergency_backups",
        "MAX_VERSIONS": "20"
      }
    }
  }
}

Cursor: Create .cursor/mcp.json with similar config.

Tools

File Operations

• backup_create: Create backup with context
• backup_list: List available backups
• backup_restore: Restore with safety backup

Folder Operations

• backup_folder_create: Backup with pattern filtering
• backup_folder_list: List folder backups
• backup_folder_restore: Restore folder structure

Management

• backup_list_all: List all backups
• mcp_cancel: Cancel operations

When to Use Backups

Only create backups when truly needed:

1. Before Refactoring: When changing important code
2. Before Removing Folders: When reorganizing project structure
3. Multiple Related Changes: When updating several connected files
4. Resuming Major Work: When continuing significant changes
5. Before Restores: Create safety backup before restoring

Keep backups minimal and purposeful. Document why each backup is needed.

Rules for Copy-Paste

Always try to use the backup MCP server for operations that require a backup, listing backups and restoring backups.
Only backup before critical code changes, folder removal, changes to multiple related files, resuming major work, or restoring files.
Keep backups minimal and focused only on files being changed.
Always provide clear context for why a backup is being created.
Use pattern filters to exclude irrelevant files from folder backups.
Use relative file paths when creating backups.
Create emergency backups before restore operations.
Clean up old backups to maintain system efficiency.
Backup tools: backup_create, backup_list, backup_restore, backup_folder_create, backup_folder_list, backup_folder_restore, backup_list_all, mcp_cancel.

For Human Users

Simple commands like these at the start you may have to mention MCP tool

# Back up an important file
"Back up my core file before refactoring"

# Back up a folder before changes
"Create backup of the API folder before restructuring"

# Find previous backups
"Show me my recent backups"

# Restore a previous version
"Restore my core file from this morning"

Agent Examples

Quick Backups

Resume Session

Core Changes

Restore Points

Manage

License

MIT