Skip to main content
Glama

Related Servers

Alternatives to handoff-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Centralized multi-project state & handoff MCP server that lets AI agents save checkpoints in one session and resume in another with minimal token overhead, including git snapshots and code-graph integration.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP server that stores durable project state — goals, validation evidence, decisions, blockers, checkpoints, and scope coverage — in a single SQLite file alongside the repository. It lets a single agent keep working across context windows, compaction, and restarts by resuming from a saved position instead of a larger context, with deterministic guardrails on goal progression and project completion.
      4 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server that persists AI coding agent memory and session context, enabling seamless resume across sessions with searchable memories and checkpoints.
      4 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Local MCP server that lets your AI coding agent query its own cross-tool project history - file/command freshness, past test failures, cost & token spend, cache status, and session handoff - over stdio, 100% local, no telemetry.
      53
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding assistants to create versioned work contracts, claim tasks with durable leases, record checkpoints and decisions, and hand off unfinished work to another supported agent. Provides independently observed verification receipts and cross-agent continuity through a local-first MCP STDIO server.
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct operation (init, save, recall, status, memory append, doctor), but recall and status both read project state, and memory_append has dual read/write behavior. Descriptions help clarify, but a minor overlap exists.

    Naming Consistency4/5

    All tools share the handoff_ prefix and use snake_case, but the command words vary in type: init/save/recall are verbs, while status and doctor are nouns, and memory_append is a compound. The style is consistent overall with minor deviations.

    Tool Count5/5

    Six tools is well-scoped for a handoff management server, covering setup, save, load, status, memory, and health check without being excessive or too thin.

    Completeness4/5

    The core lifecycle of handoff management is covered: init, save, recall, status, and health check. Missing operations like explicit delete or list of prior handoffs are minor and agents can work around them.

    Maintenance

    ActivityStale
    ResponsivenessNo issues