GhostBus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STORE | Yes | Path to the shared GhostBus store file. Pass this as the --store argument when launching the MCP server, e.g. --store /path/to/shared/ghostbus-data.json. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bus_statusC | Workspace status: agents, message/task/file counts, version. |
| bus_registerA | Register (or rejoin) this agent on the bus with a role and capabilities. First registration returns a per-agent token ONCE — store it; on a token-enforced bus it must be passed as |
| bus_rotate_tokenA | Rotate this agent's token (requires the current token on an enforced bus). The old token stops working; the new one is shown once. |
| bus_heartbeatB | Heartbeat: mark this agent present and get the live agent list with online status. |
| bus_searchB | Search messages, tasks, and shared files by text. |
| bus_channelsB | List message channels with message counts. |
| bus_agentsA | List registered agents with roles, capabilities, and last-seen times. |
| bus_sendB | Send a message to one agent (to = its name) or broadcast (to = "*"). Set threadId to reply in a thread. |
| bus_inboxA | Read messages visible to this agent (direct, broadcast, and its own). Marks them read unless markRead=false. |
| bus_threadC | Read a message thread (root message + its replies). |
| bus_create_taskB | Create a handoff task. Optionally assign it, mark urgent, or gate it behind human/agent approval (needsApproval). |
| bus_list_tasksB | List tasks, optionally filtered by status or assignee/claimer. |
| bus_approve_taskA | Approve a task that is waiting in needs-approval, releasing it to the queue. |
| bus_claim_taskA | Claim a queued task exclusively (15-minute lease). Fails if another agent holds it. |
| bus_complete_taskC | Complete a task you claimed, with a result summary for the sender. |
| bus_cancel_taskC | Cancel an open task. |
| workspace_put_fileC | Write a shared workspace file (capsule, note, deliverable). Path may not contain "..". |
| workspace_get_fileC | Read a shared workspace file. |
| workspace_list_filesB | List shared workspace files with size and last writer. |
| workspace_put_contextC | Publish the shared context object (project state every agent reads first). |
| workspace_get_contextC | Read the shared context object. |
| workspace_boardA | Render the shared board: agents, open tasks, files, recent activity. |
| bus_comment_taskC | Comment on a task (discussion lives on the task, next to its history). |
| workspace_delete_fileC | Delete a shared workspace file. |
| bus_syncA | Catch-up sync: all provenance events after a sequence number (an agent that was offline replays exactly what it missed). Returns headSeq to store as the next cursor. |
| workspace_get_capsuleB | Read a project capsule (structured shared memory: State / Decisions (locked) / Next / Session log). Creates it from the template when create=true. |
| workspace_update_capsuleB | Update one capsule section (State, Decisions (locked), Next) or append a Session log entry. Other sections are preserved. |
| workspace_file_historyB | Version history of a shared file (current version + up to 10 previous). |
| bus_eventsC | Read the provenance event log (who did what, when). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
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.
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.
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.
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.