Skip to main content
Glama

Related Servers

Alternatives to agent_bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables running both Claude Code and Codex locally with a shared task board, session resume, cross-agent handoff, and an MCP bridge for inter-client messaging and task/context inspection.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to work concurrently on the same repository by coordinating task ownership, file locks, architectural decisions, investigation gaps, handoffs, and audit activity through a local SQLite-backed MCP interface.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables multiple AI coding tools to collaboratively review code by sharing a SQLite-backed board, allowing them to create threads, post and reply to comments, list threads, and update statuses through MCP.
      16
      209 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables multiple AI coding agents on different machines to coordinate on a single codebase by atomically claiming tasks, acquiring repo-relative file locks, and exchanging messages through a shared, token-authenticated SQLite-backed board over MCP.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple coding agent sessions to form local squads where a commander dispatches tasks and executors report progress, ask questions, and receive correlated answers through MCP tools backed by a persistent SQLite message queue.
      66 npm
      1
      MIT

    TDQS

    D1.9/5.0

    Scored across 22 tools

    Disambiguation2/5

    Every tool carries the identical boilerplate description ('Execute bridge_<name> through the v2 service'), so descriptions provide zero help in telling tools apart. Names alone leave several clusters ambiguous: bridge_show/status/board/context/inbox, bridge_export/log/activity, and bridge_clean/doctor/migrate could easily be confused.

    Naming Consistency4/5

    All 22 tools use a uniform bridge_<snake_case> prefix, which is highly predictable. The only minor deviation is mixing nouns (inbox, board, context, agents) with verbs (send, claim, done) and the multi-word bridge_who_coordinates, but the pattern remains readable.

    Tool Count3/5

    At 22 tools the surface is heavy for what appears to be an agent-coordination bridge; each tool may earn its place, but the sheer number plus identical descriptions makes the set feel bloated and hard to navigate.

    Completeness3/5

    The names suggest a fairly full coordination lifecycle (send, inbox, claim, done, question/answer, review, board, activity, log, whoami, migrate, doctor), but with no meaningful descriptions it is impossible to confirm coverage. Obvious update/edit or delete/close operations for messages and tasks are not clearly represented.