Skip to main content
Glama
tulong66

agent-bus-mcp

by tulong66
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-bus-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-comms

      ahmeda14960
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables multiple AI agents to communicate and coordinate via a shared SQLite-backed message log, supporting directed messages, broadcasts, and session discovery.
      -

    • agent-handoff-mcp

      SarutobiSasuke8
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to exchange structured work items with an auditable lifecycle, supporting send, acknowledge, block, complete, and cancel operations via a shared SQLite-backed inbox.
      0
      2
      Apache 2.0

    • Local AI Relay

      zxc972
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agent hosts to exchange durable, local sender/receiver messages through a SQLite mailbox exposed as MCP tools (connect, send, receive, reply, ack, status, disconnect), so a coordinator can dispatch commands and an executor can return results without model polling while idle. A configured host wake adapter is still required to turn an incoming event into an Agent turn.
      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

    B3.4/5.0

    Scored across 6 tools

    Disambiguation3/5

    Most tools have clear, distinct purposes, but bus_inbox and bus_wait_message overlap heavily: both retrieve incoming messages and support blocking behavior. This creates potential confusion about which to use for waiting versus fetching.

    Naming Consistency3/5

    All tools share a consistent bus_ prefix, but the naming patterns after the prefix are mixed: verbs (send, register), nouns (inbox, history), and verb-object phrases (wait_message, list_agents). This reduces predictability compared to a unified verb_noun convention.

    Tool Count4/5

    Six tools is a reasonable size for an agent messaging bus, covering send, receive, polling, history, registration, and agent discovery. The slight redundancy between bus_inbox and bus_wait_message means one could potentially be removed, but the count is still well-scoped.

    Completeness4/5

    The toolset covers the core bus lifecycle: register agents, send and receive messages, wait for messages, view history, and list agents. Minor gaps exist, such as no explicit deregister/unregister operation or message acknowledgment mechanism, but these are not critical for basic bus functionality.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources