Skip to main content
Glama

Related Servers

Alternatives to Branchpoint

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to generate and retrieve a contextual document for a git branch, summarizing repository state, changes, and freshness, so they can understand the branch without scanning the entire codebase.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Persistent, structured memory for AI coding agents via a git-like filesystem with branch/commit/merge tools, enabling agents to maintain context across sessions.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.
      105
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Provides AI coding assistants with persistent project memory by capturing development checkpoints during git commits, branch switches, and inactivity. It enables seamless task resumption through tools that retrieve session history, momentum, and synthesized re-entry briefings.
      15 npm
      3
      MIT

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: ping is a health check, get_branch_context retrieves data, and save_branch_context writes data. There is no overlap or ambiguity between any of them.

    Naming Consistency4/5

    get_branch_context and save_branch_context follow a consistent verb_noun pattern, while ping is a conventional standalone health-check name. This is a minor deviation rather than a systemic inconsistency.

    Tool Count5/5

    Three tools is a well-scoped size for a focused branch-context server. Each tool serves a necessary function without redundancy or bloat.

    Completeness4/5

    The core read/write lifecycle for branch context is covered with get and save. A delete/clear operation is a minor missing capability, but the server still accomplishes its primary purpose effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues