Skip to main content
Glama
therapietech

MCP Agent Bus

by therapietech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to MCP Agent Bus

No user-submitted related servers found.

    Related Servers

    • mcp-agent-bus

      josesuarezcordova
      A
      license
      A
      quality
      A
      maintenance
      Enables local, event-driven messaging between multiple AI coding-agent sessions on the same machine using only Node.js and the filesystem, allowing them to hand off tasks, exchange replies, and broadcast announcements without external infrastructure.
      6
      MIT

    • letterbox

      dovahkiin-v
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables real-time, file-based messaging between terminal AI agents (like Claude Code, Gemini CLI) allowing them to collaborate on tasks directly without a server or network, using JSON files and atomic rename for coordination.
      20 PyPI
      MIT

    • agentsocks

      Aelethion
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code, Codex, and other coding-agent sessions on the same machine to message each other, exchange tracked tasks with owners and states, and coordinate through channels, broadcasts, and multi-session asks without typing into terminals. Messages are routed by what the receiver is doing — next tool call, end of turn, or a held-back digest — so a flood of traffic doesn't interrupt active work.
      14
      MIT
    • Dead Drop by forgeaura

      Dead Dropofficial

      forgeaura
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents on the same machine to exchange asynchronous messages as plain Markdown files, with optional wake-up notifications per agent.
      5 npm
      1
      AGPL 3.0

    • harness-summit

      anthonyleung-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agent sessions running under different coding harnesses on one machine to message each other and automatically wake idle receivers so they read the mail and reply. It stores all state as plain files under a home directory, with no daemon, network, or account required.
      439 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.1/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct operation on the message bus, and the send vs broadcast vs receive distinctions are well drawn. The only real overlap is bus_receive vs bus_peek, both returning pending messages for the caller's session; the consume-vs-non-consume wording disambiguates this well enough.

    Naming Consistency4/5

    All six tools use a consistent bus_ prefix in snake_case with an action-oriented name. Minor deviations exist: bus_broadcast names the action while bus_read_broadcasts/bus_list_sessions pair verb+noun, but the pattern remains predictable.

    Tool Count5/5

    Six tools is well-scoped for a message-bus server, with each tool earning its place (send, receive, peek, broadcast, read broadcasts, list sessions). No redundant or filler tools.

    Completeness4/5

    The surface covers the core pub/sub and point-to-point lifecycle: sending, consuming, peeking, broadcasting, reading broadcasts, and discovering sessions. Minor gaps remain (no explicit session registration/join or message deletion/ack), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources