Skip to main content
Glama

Related Servers

Alternatives to undo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      1,256 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent, 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.
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides 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.
      210 npm
      136
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude AI coding assistants to persist and restore context across sessions, save checkpoints, organize information with channels, and search or track changes so long coding workflows can continue without losing decisions and progress.
      210 npm
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues