undo-mcp
Related Servers
Alternatives to undo-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents and their users to roll back unwanted file changes by recording workspace state before, during, and after a turn and restoring it selectively. It supports undoing, redoing, and diffing turns across Claude Code, Codex, Gemini CLI, Cursor, OpenCode, and Antigravity CLI.58 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code and other AI coding assistants to save, search, and restore context across sessions through channels, checkpoints, and snapshots. Preserves work history, decisions, and progress so conversation compaction or resets no longer lose critical information.228 npmMIT
- AlicenseNot gradedqualityDmaintenancePersistent, shared memory for Claude across sessions and clients (Code, Desktop, Cowork) — deterministic diff reads, checkpoints, cross-client task handoff, and project-wide search. 100% local and deterministic, no API keys, no LLM summarization.4MIT

statecli-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceGives AI agents memory, undo, and self-awareness by tracking file changes and enabling checkpoints and rollbacks.59 npm2MIT- AlicenseNot gradedqualityAmaintenanceProvides persistent context management for Claude AI coding assistants, enabling users to save, search, checkpoint, restore, and share project context across sessions and parallel sessions. It preserves work history, decisions, and progress so coding workflows survive compaction and context limits.228 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent context management for Claude AI coding assistants, allowing you to save and restore conversation context, create checkpoints, and organize information across sessions to prevent losing important work history and decisions during long coding sessions.228 npm136MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: checkpoint creates a checkpoint, cleanup clears checkpoints, list_undos lists them, status provides system status, and undo performs the undo operation. The descriptions make it unambiguous which tool to use for each action.
All tools follow a consistent naming pattern: checkpoint, cleanup, list_undos, status, and undo. They use clear, imperative verbs that directly describe their function, with no mixing of conventions or styles.
With 5 tools, this server is well-scoped for its undo system purpose. Each tool serves a specific role in the checkpoint/undo lifecycle, and there are no extraneous or missing tools for this focused functionality.
The tool set provides complete coverage for the undo system domain: checkpoint creation, cleanup, listing, status checking, and undo execution. There are no gaps in the CRUD/lifecycle operations needed for this functionality.