/mcp (bro)
All mechanics live in the bro CLI. This skill is policy only.
bro fleet mcp serves the plane catalog (specs/bro-9rls.1.md) over stdio MCP.
One server reaches every MCP-capable client — no per-client adapter.
Tools are generated from the plane descriptors, never hand-maintained:
bro_<plane>_list and bro_<plane>_get on every plane, plus one tool
per declared named read (bro_work_ready, bro_queue_next,
bro_gates_status, bro_gates_threads, bro_agents_fleet,
bro_events_tail, bro_judge_stats, bro_debt_next,
bro_debt_summary, bro_learn_probe).
Every tool mirrors a CLI command — the transport is an adapter
over the CLI contract, never a parallel surface (spec bro-xiq2m). Each
plane op declares its twin in the descriptor's cli map, and
bro contract check fails CI on an op without one:
| Tool | CLI equivalent |
|---|---|
bro_work_ready |
bro next --list |
bro_work_status |
bro status |
bro_agents_backends |
bro agents status |
bro_agents_fleet |
bro fleet |
bro_agents_delegate |
bro fleet delegate |
bro_queue_next |
bro convoy next |
bro_gates_status |
bro act status |
bro_gates_threads |
bro act threads |
bro_events_tail |
bro bus subscribe |
bro_events_lifecycle |
bro bus subscribe |
bro_events_activity |
bro watch |
bro_judge_stats |
bro judge stats |
bro_debt_next |
bro debt next |
bro_debt_summary |
bro debt summary |
bro_learn_probe |
bro learn probe |
The events reads are richer than their twins: bro_events_tail merges
broker replay, mailbox drops, and lifecycle rows; bro bus subscribe
streams broker rows only — subscribe gets you the live leg, the tool
gets you the merged replay.
Read-only except spec-assigned verbs. Write verbs stay unexposed
until a spec assigns one to this transport through the descriptor's
mcpVerbs allowlist — generation is the only path, so a verb cannot
become a tool by accident. The one wired verb today is
bro_agents_delegate (spec bro-z8tng — the same contract as
bro fleet delegate: mode:'wait' is a pooled ACP turn, 'detach' a
registry spawn); spawn/stop/respawn remain declared-but-unwired.
Registering
bro fleet mcp runs in the repo it should serve (the catalog is per-dir).
Point the client's MCP config at it like any stdio server:
{ "mcpServers": { "bro": { "command": "bro", "args": ["mcp"], "cwd": "<repo>" } } }
Semantics the client can rely on
tools/listis the discovery document: an absent capability means an absent tool — a repo with no review host exposes nobro_gates_*tools, a repo without beads nobro_queue_*/bro_learn_*.- Tool results are JSON text. A plane whose backend is down returns
{ "error": "<degraded note>" }(withisError: true) — degraded, never a stack trace, never a fake empty list. get/execrefs are the domain's stable keys — task id, agentId, mol id,{gen}:{seq}, thread_id.mcp.planesin bro.config.json narrows exposure: absent/emptymcpsection = every read plane (spawning the server IS the consent),[]= none, a list = allowlist.
Debug surface
| Command | What it does |
|---|---|
bro fleet mcp --tools |
prints the generated tools/list payload for this repo (same capability gating a client sees) and exits |