Skip to main content
Glama
Sign In
mariomosca

agent-bus

by mariomosca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-bus

No user-submitted related servers found.

    Related Servers

    • hato

      severzemlya
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables inter-session messaging for Claude Code, allowing sessions on different machines to send messages to each other, with delivery as user turns and support for offline queuing.
      406 npm
      MIT

    • coordinator

      MT-gar
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables multiple Claude Code sessions to communicate, share state, and coordinate tasks through session management, message passing, and task scheduling, supporting a three-role collaboration workflow.
      2
      MIT

    • Agent Link

      Brandon-Gottshall
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables one AI coding agent to discover, read, message, and wait on other agent sessions across Codex threads and Claude Code or Claude Desktop sessions, while logging every send as a local receipt that can be audited later.
      2 npm
      MIT

    • claude-bridge

      SnakeO
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Codex and local Claude Code sessions to exchange messages in both directions, letting Codex list sessions, send messages, and receive replies as new turns while Claude sessions can message Codex threads.
      353 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility: status for live sessions, inbox for pending messages, read for full message detail, send for delivery, archive for resolution, and thread for chronological replay. No two tools overlap in purpose or would cause an agent to misselect.

    Naming Consistency5/5

    All tools follow a uniform bus_<action> pattern, making the API predictable and easy to navigate. The action terms are concise and match their functions.

    Tool Count5/5

    Six tools is well-scoped for a message bus: enough to cover the full interaction lifecycle without redundancy. Each tool serves a distinct, necessary operation.

    Completeness5/5

    The set covers the core message lifecycle fully: send, receive, read, archive, inspect status, and replay threads. Broadcast delivery and per-session targeting are handled through bus_send, and archive provides a clean closure mechanism.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources