bus-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BUS_MCP_LIVE | No | Set to 1 to run the real-network smoke test | |
| BUS_MCP_BASE_URL | No | Base URL of the coordination bus | http://127.0.0.1:8100/api/bus |
| BUS_WRITE_SECRET | No | Same var the bus itself reads to arm write-auth (v1.1). When set here, every write tool call sends X-Bus-Secret: <value> automatically. | |
| BUS_MCP_TIMEOUT_S | No | Per-request timeout (seconds) | 10.0 |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_messageA | Append one message to the coordination-bus blackboard (append-only). v1 stores action_flag but performs no action -- it is display-only, seen by a human watching the command-center panel. |
| read_messagesA | Recent bus messages, newest first, optionally filtered by topic. |
| claim_laneA | Claim a coordination lane before starting work in it: claim-if-free, steal-if-lease-expired, renew-if-you-already-own-it. A 409 (lane held live by another owner) comes back as a clean ok=False conflict, not a crash. The bus may grant a shorter lease than requested (server-side ceiling, coordination-bus v1.3+): on ok=True the response's top-level |
| release_laneB | Release a coordination lane you hold. A 409 (held live by another owner) comes back as a clean ok=False conflict, not a crash. |
| heartbeat_laneA | Renew the lease on a coordination lane you hold live. A 409 (not held live by you) tells you to (re)claim instead of crashing. Like claim_lane, renewal is subject to the same server-side lease ceiling (coordination-bus v1.3+): on ok=True the response's top-level |
| get_bus_statusA | Roll-up for the command-center panel: active lanes, orphaned/stale claims, recent messages, pending display-only action flags. Also exposes |
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 6 tools
Each tool targets a distinct operation: posting versus reading messages, claiming, releasing, heartbeating a lane, and getting bus status. Their descriptions are detailed and uniquely identify each tool's purpose.
All tool names follow a consistent snake_case verb_noun pattern (post_message, read_messages, release_lane, claim_lane, heartbeat_lane, get_bus_status), making them predictable.
Six tools is appropriate for a coordination bus: two for messaging, three for lane lifecycle management, and one for status. No obvious over- or under-coverage.
The tool set covers the core operations of the bus: message production/consumption, lane claiming/releasing/heartbeating, and status introspection. No obvious gaps given the append-only messaging and lane management domain.