MCP tools

The server-generated coding-agent prompt for one item — the same text the CLI hands an agent.

A plan with the proposals it bundles: what the planner actually proposed, not just how much.

What became of a submitted planning job — its state, and how many proposals it produced.

A project's planning preconditions — established, code connected, indexed, repo set — before you plan.

One item in full — description, status, parent and children, dependency edges, and a readiness verdict.

One page of an item's discussion and change trail: comment threads and history, interleaved.

Every project this token can reach, each with the projectKey every other tool takes.

The ready-to-start set for a project — every item whose dependencies are all satisfied, paginated.

A project's sprints with state, goal, window and issue count, and the ids the sprint tools take.

The single highest-ranked ready item, as a full dispatch payload. The “what do I do next” call.

Search a project's items with the same filter grammar the advanced filter builder writes.

Has this already been built? Search by MEANING rather than substring — keys, titles and scores only.

The whole project's tree shape in one read — every item's key, kind, title, status and parent, with no paging loop.

Would approve TAKE this plan, and is it finishable? Both, before `final: true` — nobody else will ask.

Is this sprint finishable? Names every in-sprint item still gated by work outside it.

Is this epic, story, task or bug finishable? Names the out-of-subtree work still gating it.

Who this token is: the owning user, the active workspace, and the scopes granted. Call it first.

Search recorded lessons by meaning — the shared corpus and this project's own — before you plan or build.

Record a lesson for this project, so later plans for it are given the lesson. This project only.

Record that a lesson you found describes something that just went wrong — whether or not you also change it.

Put a file ON a work item — a research findings document, a review’s notes — so a reader sees the deliverable on the work item instead of hunting for a pull request.

Reclassify a leaf's kind when it is mis-filed — subtask to task, and back.

Atomically claim the next ready subtask in the active sprint and flip it to In Progress. Race-safe.

Atomically claim ONE named work item and flip it to In Progress. A lost claim says WHO holds it.

Close out a session branch after its PR merged: every item recorded on it moves to Done.

Open a plan to propose into — the reviewable container an agent fills instead of writing items.

Create an epic, story, task, bug or subtask; points, estimate, type, executor and repo in one call.

Declare which work item a pull request delivers — call it right after opening one, once per work item it delivers. The association is a SET, so a second call ADDS rather than moving, and it works before any webhook delivery has arrived.

Create an edge between two items — blocked_by is the one that holds an item out of the ready set.

Record that an item's work landed — the branch, the PR and the commit that carried it.

Re-parent an item, enforcing the kind-parent matrix and refusing a cycle.

Put the design RESULT on a design work item — the note sections you changed, the mock and the .png export, in one call. It is the deliverable a reviewer opens, and nothing else publishes it.

Move an item to another status. An illegal move comes back naming the ones that are legal.

Undo ONE `link_pull_request` — remove the delivery recorded between a work item and a pull request. A delivery is a row, so re-linking the right work item ADDS rather than corrects; this removes exactly the one pair you name and leaves every other delivery alone.

Remove an edge, given the same relationship used to create it.

Edit any subset of an item's fields, including the explanation body create cannot set.

Soft-remove an item: it leaves the ready set and search, and stays fully restorable.

Restore an archived item — the inverse of archive.

Permanently delete an item and its whole subtree. Irreversible, and off by default.

Post a Markdown comment as the token owner. Mentions notify the member named.

Complete the active sprint.

Create a planned sprint on a project, with an optional name, goal and planned window.

Delete a planned or complete sprint.

Move items out of their sprint and back to the backlog.

Add items to a sprint in one atomic move, appended in the order given.

Start a planned sprint, making it the project's active one.

Rename a sprint, change its goal, or adjust its planned window.

Add one turn to a project's planning conversation — what you want changed about the plan.

Submit an AI expansion of one container item. Spends the owner's credits; proposals await approval.

Open — or resume — a project's planning conversation, and read its thread.

Send the conversation's accumulated intent to the planner as one change set.

Append proposals to a plan — or close it with an empty final batch; ids come back in order, so the next batch can hang children off them.

Fill in a proposal you appended — the deepen turn, while the plan is still being written.

Correct a proposal — including its parent, its dependency edges and its repo pin (name and role) — even after the plan is in review.

Take one proposal off a plan, instead of asking a reviewer to decline the whole thing.