mcp

/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).

Read-only in v1. Write verbs stay unexposed until the spec's session-authz question is designed — a claim/resolve/spawn call is not a tool, and cannot become one by accident because generation is the only path.

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/list is the discovery document: an absent capability means an absent tool — a repo with no review host exposes no bro_gates_* tools, a repo without beads no bro_queue_*/bro_learn_*.
• Tool results are JSON text. A plane whose backend is down returns { "error": "<degraded note>" } (with isError: true) — degraded, never a stack trace, never a fake empty list.
• get/exec refs are the domain's stable keys — task id, agentId, mol id, {gen}:{seq}, thread_id.
• mcp.planes in bro.config.json narrows exposure: absent/empty mcp section = 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