Skip to main content
Glama

Related Servers

Alternatives to Claude Checkpoint MCP

  • A
    license
    A
    quality
    A
    maintenance
    Basic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md
    12
    18,541 PyPI
    4,422
    AGPL 3.0

Related Servers

  • 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.
    250 npm
    136
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides persistent context management for Claude AI coding assistants, enabling users to save, search, checkpoint, and restore work history, decisions, and progress across sessions.
    250 npm
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Provides 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.
    250 npm
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Local-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.
    23
    21 npm
    4
    MIT

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools are the exact inverse of each other: save_session_checkpoint writes state, load_session_checkpoint reads it. There is no plausible scenario where an agent would confuse the two, and the descriptions reinforce the trigger conditions for each.

Naming Consistency5/5

Both tools follow a strict verb_noun pattern (save_session_checkpoint / load_session_checkpoint) on the same object, so the pair reads as a coherent symmetric API.

Tool Count4/5

Two tools is on the thin side, but the domain is genuinely narrow — persisting and restoring a single checkpoint file — so a save/load pair is the natural minimum surface and each tool clearly earns its place.

Completeness4/5

Save plus load covers the core lifecycle: checkpoint on milestones and restore on a fresh session. Minor gaps exist (no delete/clear, no listing or diffing of multiple historical checkpoints), but a single-file design means agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive