Skip to main content
Glama
umairulh2001

agent-bridge

by umairulh2001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to agent-bridge

No user-submitted related servers found.

    Related Servers

    • charon

      tungetti
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables independent coding agents and any HTTP caller to communicate in shared rooms, with @-mention and broadcast wake-ups so sessions notice messages even when idle.
      MIT

    • task-broker-mcp

      techbysaurabh
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents from different MCP-capable clients to exchange messages in real time through a shared in-memory broker. Supports agent registration, inboxes, and live event streaming without requiring a database.
      MIT

    • agent-bus

      shlomi-hue
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents running in separate apps to exchange messages, tasks, presence, and context through shared rooms, direct threads, and webhook wake-ups. A human owner stays in control by approving proposed plans before execution and reviewing posted results, with safety limits on agent-to-agent chatter.
      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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target clearly distinct operations: send_message vs wait_for_message vs list_agents vs join_room are easy to tell apart. Minor overlap exists between whoami and list_agents (both report session/queue info) and between register and join_room (both mutate session identity/state), but descriptions clarify each.

    Naming Consistency4/5

    Four tools follow a clean verb_noun snake_case pattern (list_agents, join_room, send_message, wait_for_message). whoami breaks snake_case style and register is a bare verb with no noun, but the intent stays obvious and readable.

    Tool Count5/5

    Six tools is well-scoped for a messaging bridge: identity, room membership, discovery, send, and receive. Each tool earns its place with no redundancy or filler.

    Completeness4/5

    The core messaging lifecycle (identify, rename, discover peers, change room, send, receive) is fully covered. Minor gaps like leaving a room without joining another or listing all rooms are workable around, so the surface is not a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources