MCP Server Shipped
File and scope work without leaving the session
Your agent can look up the zone map, drop a request into Triage, draft the four fields and read the board — all from inside the conversation it is already having. What no tool here can do is open a zone or approve an access request; a transition is a question put to the gate, never a power the tool holds.
Connect it
cycle mcp # serves the tools over stdio, for a client's .mcp.jsonIt ships inside the CLI binary rather than as a second install, so there is one implementation and not two that drift. The Claude Code plugin wires it up for you.
The five tools
| Tool | What it does |
|---|---|
cc_zones | The zone map as the board holds it — paths, risk, owners |
cc_intake | One line into Triage. It does not start anything |
cc_interview | Draft the four fields, reconciled against the real zone map |
cc_scope | Save those four answers onto the task |
cc_status | A single task, or everything in flight. Read-only |
Four more on the connector
The board issues a per-machine HTTP connector, and it adds cc_setup,cc_start, cc_submit and cc_close. Each transition is a question the gate answers by the same rules the console obeys — a client of the gate, never a second door. The reference keeps the two surfaces side by side.
The line they do not cross
There is no grant and no resolve. No tool on either server issues a grant, approves access, or decides a transition — cc_start asks, the gate answers — and that absence is as much of the contract as what is present.
The reason is not caution, it is arithmetic. An approval arriving through a tool the agent calls is authenticated by a token the agent holds, so a board could not tell your yes from the agent's own. A gate an agent can call is not a gate. The tools ask; the gate decides; approvals travel only through a browser where you are already signed in.
Where it stops
- It never decides what the hook decides. Enforcement is local and offline; this server is not in that path and an outage cannot open a zone.
- It holds no second copy of the gate's rules. The day it starts judging whether a spec is complete, it can disagree with the gate — and a tool that disagrees with the gate is worse than no tool.
- It reads the board, not your disk. For what is open on this machine right now,
cycle statusis the honest answer; the grant is local and this server deliberately cannot see it.
Tool payloads are in the MCP reference, and the model they describe is the zone map.