home / mcp / rewind mcp server
Checkpoint-based server enabling undo, multi-file restores, and quick state management for Claude Code workflows.
Configuration
View docs{
"mcpServers": {
"khalilbalaree-rewind-mcp": {
"command": "node",
"args": [
"/absolute/path/to/Rewind-MCP/dist/index.js"
]
}
}
}Rewind MCP is a lightweight checkpointing server that integrates with Claude Code to automatically create and manage project state checkpoints before changes. It enables fast multi-file restores, complete undo capabilities, and a smooth workflow when you want to experiment or iterate without risking permanent code drift.
You interact with Rewind MCP through an MCP client. Before the agent makes any changes you can request a checkpoint, describe what you want to do, and then either proceed or rewind as needed.
Key patterns you’ll use include creating a checkpoint before modifications, letting the agent apply changes, inspecting the list of available checkpoints, and undoing or rewinding to a previous state when necessary.
Practical workflow example you can follow: create a checkpoint labeled with a description such as "Before adding error handling", ask the agent to implement changes, and if you need to revert, request an undo to restore the previous state.
Available actions you can perform through the MCP client include: checkpoint(files, description) to create a new checkpoint, undo(file) to restore to a previous version, list_undos() to view saved checkpoints, cleanup to remove all checkpoints, and status() to see the current checkpoint status.
# Prerequisites
- Node.js installed
- Git installed
# Step 1: Clone the project repository
git clone https://github.com/khalilbalaree/Rewind-MCP.git
cd Rewind-MCP
# Step 2: Install dependencies
npm install
# Step 3: Build the server
npm run buildRewind MCP runs as a local server you invoke via Node. You configure Claude Code to start the MCP when needed by pointing to the built entry point.
User-based configuration (global): add a server reference to your Claude Code MCP configuration so the client can run the local server. Use the absolute path to the built entry file.
Project-based configuration (alternative): create a .mcp.json in your project directory to share with teammates or keep under version control.
Example configuration blocks are shown below for reference. Replace /absolute/path/to/Rewind-MCP/dist/index.js with the actual path on your machine.
{
"mcpServers": {
"Rewind-MCP": {
"command": "node",
"args": ["/absolute/path/to/Rewind-MCP/dist/index.js"],
"env": {}
}
}
}As you work, you can inspect the available checkpoints to decide where to revert. Restoring a checkpoint brings back files to the exact state they were in at that moment, including both additions and deletions.
If you want to share a specific checkpoint with teammates, describe it clearly when you create it, and use list_undos() to review the available options before deciding to rewind.
Keep checkpoints concise and descriptive to make it easy to identify the state you want to restore. Regularly cleanup old checkpoints when they are no longer needed to avoid clutter.
When testing new changes, create a checkpoint first, then apply your changes. If something breaks, you can rewind back to the checkpoint with a single command.
Create a new checkpoint before applying further changes to the project state.
Restore files to a previous checkpoint, effectively undoing recent modifications.
List all available checkpoints with descriptions for easy selection.
Remove all stored checkpoints to reclaim space and reduce clutter.
Show the current checkpoint status including the active checkpoint.