Skip to main content
Glama
StoneReaper

openhandoff-mcp

by StoneReaper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openhandoff-mcp

No user-submitted related servers found.

    Related Servers

    • Memory Fabric

      elViRafa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding assistants to store and retrieve project-aware context as plain Markdown files locally, with no cloud or vector database required.
      1
      MIT

    • LumenCore

      arclightdynamics
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
      4 npm
      Apache 2.0

    • MCP Memory Keeper

      luciabertrand7746
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to persistently save, search, and restore project context across sessions, including decisions, progress, file caches, checkpoints, and channel-based memory. It supports git-aware organization, batch operations, and shared memory across parallel sessions.
      250 npm
      MIT

    • MCP Memory Keeper

      dorisjain
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to maintain persistent context across sessions by saving, searching, organizing, checkpointing, and restoring conversations, decisions, file content, and progress.
      250 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct action: loading the handoff, saving new checkpoint data, searching within it, and packing a context slice. There is no overlap or ambiguity between these four operations.

    Naming Consistency4/5

    All tools follow a clear verb_noun pattern (load_handoff, save_checkpoint, search_handoff, pack_context). The only minor inconsistency is the use of different nouns (handoff, checkpoint, context) when referring to related concepts, but the pattern remains uniform and predictable.

    Tool Count5/5

    With only 4 tools, the server is tightly scoped for its purpose of managing agent handoffs. Every tool serves a distinct, necessary function and none feel superfluous.

    Completeness4/5

    The set covers core lifecycle operations: load, save, search, and context packing, which likely handles most workflows. A minor gap is the lack of a clear delete/reset operation for the handoff, but this may not be needed in the intended use case.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources