Context Travel MCP
Related Servers
Alternatives to Context Travel MCP
No user-submitted related servers found.
Related Servers
- 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.206 npm136MIT
- AlicenseAqualityAmaintenanceLocal-first working-state checkpoints and portable handoff packets for AI coding agents. Continuation checkpoints recover Claude Code sessions after rate limits, crashes, and compaction; packets hand tasks across tools, repos, and machines — Markdown on disk, no cloud, no telemetry.2321 npm4MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to persist and restore checkpoint state, supporting crash recovery and replay for LangGraph-based workflows.8-
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to commit stateful workflow checkpoints by calculating state hashes and rollback points through the Model Context Protocol. It provides deterministic, dependency-free checkpoint management for autonomous agent execution.8-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain context across conversation sessions by saving and retrieving summaries of key points from past interactions.334 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-assisted coding tools to checkpoint sessions, detect context drift, and restore an earlier state while preserving uncommitted work and generating a recovery handoff for an informed restart.MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.