Skip to main content
Glama
khalilbalaree

undo-mcp

by khalilbalaree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to undo-mcp

No user-submitted related servers found.

    Related Servers

    • claude-continuity-mcp

      gabicacabelos
      A
      license
      Not graded
      quality
      B
      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

    • MCP Memory Keeper

      mkreyman
      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.
      122 npm
      135
      MIT

    • Rewindex

      crsxmd
      F
      license
      Not graded
      quality
      C
      maintenance
      Auto-snapshot tool for AI agents. Reduces the risk of AI agents breaking your code by automatically saving a snapshot of every file change locally. Rewind sessions, audit code changes, and inspect diffs directly from your AI chat or the built-in dashboard. Free and safe no cloud run local.
      1
      -

    • agentvc

      nintechio
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to checkpoint workspace state, branch parallel attempts, inspect diffs, and roll back to known-good states mid-task through MCP tools, with automatic safety checkpoints to prevent data loss.
      4 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    Resources