Skip to main content
Glama
Sign In
GhostBus

GhostBus

by littlestjames82-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to GhostBus

No user-submitted related servers found.

    Related Servers

    • Agent Router MCP

      dazhi666666
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets any MCP-capable agent client join a shared local collaboration space with a common task board and mailbox, so agents can publish, claim, and track tasks with dependencies and message each other or the human. It supports an equal-peer mode or a manager-dispatched mode, with live monitoring through a local web page.
      9 npm
      3
      MIT

    • multi-agents

      toroc07
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables multiple AI agents using MCP-compatible clients to collaborate in parallel on the same project across one or more machines, with direct messaging, a shared task board, atomic file/folder locking, presence tracking, and a live web dashboard.
      1
      MIT

    • Council Blackboard

      aetheris-consulting
      F
      license
      C
      quality
      B
      maintenance
      Enables AI agents to collaborate via shared blackboard state, multi-agent deliberation, human-in-the-loop proposal approval, operating-mode control, and audit logging through MCP.
      11
      -

    • Bcontext

      Ibonarambarri
      A
      license
      Not graded
      quality
      A
      maintenance
      Exposes a self-hosted shared workspace over MCP where AI agents and their teammates read and write tasks, decisions, docs and results, so each session picks up where the last one left off. It adds hybrid cited search, per-workspace OAuth or scoped tokens, change feeds for cheap re-sync, and an append-only audit trail of every agent or human write.
      AGPL 3.0
    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

    B3.1/5.0

    Scored across 29 tools

    Disambiguation4/5

    Tools are mostly clearly differentiated by resource and action across messages, tasks, files, context, capsules, and events. Minor overlap exists among bus_agents, bus_heartbeat, and bus_status for agent/presence information, and bus_inbox versus bus_thread both read messages, but descriptions clarify the boundaries.

    Naming Consistency4/5

    The set follows a consistent two-prefix scheme (bus_* and workspace_*) with verb_noun action tools such as bus_send, bus_create_task, and workspace_put_file. Some noun-only names like bus_status, bus_inbox, and workspace_board are minor deviations but remain readable and well-grouped.

    Tool Count3/5

    29 tools is heavy for a single MCP server, though the multi-agent collaboration domain is broad and most tools map to distinct operations. Some consolidation is possible around agent presence/status/board and message-reading tools, making the surface over-rich but not unreasonable.

    Completeness4/5

    The surface covers messaging, tasks, files, shared context, capsules, events, and sync with lifecycle operations for most resources. Gaps include no agent deregistration, no message edit/delete, and no general task-update/reassign tool, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources