Skip to main content
Glama

Related Servers

Alternatives to Context Travel MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables long-running autonomous agents to snapshot environment and context states, evaluate the viability of competing reasoning branches, and roll back to an earlier checkpoint when an exploration path fails without restarting from scratch. Exposes this tree-of-thoughts state management over the Model Context Protocol for use in Claude Desktop, Cursor, and custom agentic frameworks.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to keep project state, evidence, and decisions bound to the repository, and to resume work across sessions and hosts by receiving a bounded, revalidated context packet instead of a full transcript. It also lets agents record checkpoints, handoffs, and closeouts while keeping deterministic decision and routing authority in code.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude and other AI agents to store decisions, patterns, and knowledge once and retrieve relevant context automatically across sessions, surviving context limits, restarts, and compaction.
      6 npm
      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.
      131 npm
      136
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI coding assistants to save, search, checkpoint, and restore context across sessions so work history, decisions, and progress persist through conversation compaction or session resets.
      131 npm
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct and non-overlapping purpose: checkpoint_context saves context, delete_checkpoint removes it, get_context_stats provides metrics, list_checkpoints enumerates saved states, and reset_to_checkpoint restores to a checkpoint. There is no ambiguity in tool selection.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., checkpoint_context, delete_checkpoint, get_context_stats, list_checkpoints, reset_to_checkpoint). The naming is uniform and predictable across the set.

    Tool Count5/5

    With 5 tools, the server is well-scoped for managing context checkpoints, covering creation, deletion, listing, restoration, and monitoring. Each tool earns its place without being excessive or insufficient.

    Completeness5/5

    The tool set provides complete lifecycle coverage for context checkpoint management: create (checkpoint_context), read (list_checkpoints, get_context_stats), update (reset_to_checkpoint), and delete (delete_checkpoint). There are no obvious gaps for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues