Skip to main content
Glama
josesuarezcordova

mcp-agent-bus

by josesuarezcordova
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-agent-bus

No user-submitted related servers found.

    Related Servers

    • letterbox

      dovahkiin-v
      A
      license
      Not graded
      quality
      A
      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.
      23 PyPI
      MIT

    • claude-intercom-mcp

      dataforxyz
      A
      license
      A
      quality
      B
      maintenance
      Enables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.
      8
      14 npm
      2
      AGPL 3.0
    • 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

    • agent-mailbox

      polaris-smart
      A
      license
      B
      quality
      B
      maintenance
      Enables local AI agents on the same machine to exchange messages asynchronously through mailboxes, with tools for registering, sending, replying, checking, broadcasting, and waiting for messages without polling or cloud services.
      9
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct purpose: sending to a specific session, receiving/consuming, peeking without consuming, broadcasting to all, reading broadcasts with cursor advancement, and listing sessions. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent 'bus_<verb_noun>' pattern (e.g., bus_send, bus_receive, bus_read_broadcasts). Names are lowercase with underscores, making them predictable and easy to reason about.

    Tool Count5/5

    Six tools is well-scoped for a messaging bus, covering send, receive, peek, broadcast, read broadcasts, and session listing without unnecessary additions. Each tool earns its place.

    Completeness5/5

    The tool surface covers the core lifecycle of inter-agent messaging: sending, receiving (consuming), peeking, broadcasting, reading broadcasts, and discovering sessions. No obvious gaps that would cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources