Skip to main content
Glama
agent-context-bridge

agent-context-bridge

Related Servers

Alternatives to agent-context-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An MCP server and CLI that keep project decisions, their reasons, learnings, and next steps in a local SQLite record. AI agents can retrieve earlier context, record project choices, and resume work across sessions; ordinary local use needs no dashboard account.
      15
      577 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Persistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables two local coding agents to read each other's user-visible history, search past decisions with source tracing, and save confirmed conclusions into a shared memory. Also supports credential-status checks and limited task handoff between Codex and Antigravity over MCP stdio.
      MIT

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: acb_search queries records, while acb_status reports workspace/store health. There is no plausible overlap in selection, and the descriptions reinforce the boundary between search and diagnostics.

    Naming Consistency5/5

    Both tools use the same acb_ prefix and a consistent lowercase snake_case noun/verb style. The naming pattern is predictable and easy to extend.

    Tool Count3/5

    Two tools is thin for a bridge/server that implies shared context lifecycle operations beyond read-only search and diagnostics. The small surface is coherent but leaves the server feeling like a partial read-only facade.

    Completeness2/5

    The surface lacks write/append/inject/list/prune operations despite references to an 'inject' workflow and a shared context store. Agents can inspect or search existing context but cannot create or manage records, which is a significant lifecycle gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues