MCP-tools

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

The decision a person made on one approval gate — the note they wrote when they sent your work back, who wrote it, when, and on which version.

The APPROVED design of one design card, with short-lived links to its files — or which of five reasons there is none.

A plan with the proposals it bundles: what the planner actually proposed, not just how much — including a proposed obsolescence mark (current → proposed, with its note) and its supersedes edges, named by key.

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 or folder, children, dependency edges, a readiness verdict, the errors linked to it, and the latest refusal sent back on it.

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

What a card is meant to be built against (`blockersOf`), or a page of the project’s approved designs. No links — take those from `get_design`.

Every folder of a project in one read — each folder's id and its path — to find a folder by name.

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

Takes no arguments.

One ready LANE of a project, paginated — leaves (default, never a bug, each naming its container), runnable containers, or bugs — in the order the Ready view shows.

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

Read a work item’s to-do list: its steps in order, which are done, and the progress.

The next item of one ready lane — a leaf (default, never a bug) or a bug as a full dispatch payload, or the next runnable container for a parent run. 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, parent, folder and obsolescence mark, with no paging loop.

Would approve TAKE this plan, is it finishable, is every edge on one level, and do its cross-parent edges have their parent edges? All four, 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, is every edge on one level, and do its cross-parent edges have their parent edges? Names what is missing.

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

Takes no arguments.

Search recorded lessons by meaning — the shared corpus and this project's own — narrowed by kind, type, phase and subject, 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.

Append one step to the end of a work item’s to-do list.

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: assign it to you and flip it to In Progress.

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

Take over a work item whose last run died or stopped at a gate that is now approved, as `motir continue` does: its branch and pull requests, not a fresh start.

Take the repair lock on a work item with failing pull requests, as `motir fix` does. One fixer at a time.

End your continue of a work item with how it went, so the page shows it and the card can be continued again.

End your repair of a work item with how it went, so the page shows it and a new repair may start.

End your run of a card with how it went; a delivered close records you as the implementer.

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

Mint a short-lived presigned PUT for a story’s acceptance recording — step 1 of 2, because a video is far larger than a tool argument can carry. Upload the bytes straight to the store, then register the pathname.

Mint a short-lived presigned PUT for a design asset too large to send inline — step 1 of 2, because a large asset is more than a tool argument can carry. Upload the bytes straight to the store, then publish the pathname. Refuses a screenshot, a card nothing waits on, and a done design card.

Create a folder at the root or inside another folder; names are unique per level.

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

Create an epic, story, task, bug or subtask under a parent or in a folder; points, estimate, type, executor, difficulty, repo and obsolescence mark in one call.

Delete a folder; its folders and work items move up, and the result lists what moved.

Permanently delete one step of a work item’s to-do list.

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-place an item — under a new parent, or into or out of a folder — enforcing the kind-parent matrix and refusing a cycle.

Move one step of a work item’s to-do list to a new position.

Register the uploaded recording as the story’s acceptance receipt — the thing a reviewer watches and the gate rests on. Nothing else publishes it, and a missing publish looks exactly like a successful run.

Publish a page as a decision card’s decision: seals its newest version and, on an agent card, asks a person to approve it.

Put the design RESULT on a design work item — the mock(s) and the area note as a link, what a reviewer opens — only when an open work item is blocked_by the design. No .png and no inline note: both are refused, and so is a done design card, which accepts no new version. Each asset arrives inline as base64, or as the pathname of a create_design_upload grant when it is too large to send.

Put a RUN’s HOW TO TEST onto its run target — before the run finishes, and again when a later commit changes a step: rich-text Markdown with sections and every command in a fenced code block (click-to-copy), plus the commit of each repository it pushed to.

Say the step you are about to take on a card, record a milestone, or send a heartbeat for your open runs.

A dispatched runner reports the card it stopped on as unbuildable — acknowledged, nothing to act on.

Tick or untick one step of a work item’s to-do list. Ticking the last step does not change the work item’s status.

Open your own run of a card you hold, naming your harness and model, so it shows on Runs and on the card.

Keep your continue of a work item alive. A continue silent for five minutes is closed and its lock released.

Keep your repair of a work item alive. A repair silent for five minutes is closed and its lock released.

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.

Rename a folder, or move and reorder it — one or the other per call, never both.

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

Edit one step of a work item’s to-do list. Only the fields you send change; null clears an optional one.

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.

Permanently delete a comment you wrote, with its replies. Only its author can delete it here.

Replace the body of a comment you wrote. Only its author can edit it here.

Read one page as markdown — its title, where it is filed, its revision and newest version — to read it or to write it back; or read one version by number.

Create a page with a markdown body — at the root, in a folder or as a sub-page — and get its id and revision.

Replace a page’s whole body with markdown at the revision you read; a page saved since is refused, not merged.

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 planning conversation, named by its session id — what you want changed about the plan.

The hosted code graph around a query — the hosted planner's own answer, paged, every absence a named state.

Symbols matching a name in the hosted code graph — the hosted planner's own answer, paged.

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

Each repository's index state, latest code-health audit summary and derived coding convention — what the hosted planner reads.

Open a planning conversation — by its id, your recent one, or a new one — and read its thread.

One file's text from a repository in the project's set, at a ref — capped and line-ranged like the hosted planner's read, every absence a named outcome.

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

Append proposals to a plan — close it with an empty final batch, or add to one you already closed with `revision: true`; ids come back in order, so the next batch can hang children off them. A `modify` may also mark a FINISHED card outdated or deprecated, with a note and supersedes edges (an `add` names the cards it replaces in `supersedesRefs`), refs as a key, an id or a `planItem:` ref; marking an unfinished card is refused — remove it instead.

Is this card still what its last approved plan approved? Its plan history and the verdict.

Record WHY an unapproved plan had to change — four branches, two of which file a planning bug; it changes nothing about the plan.

Report the step a planner session is on (settle, lay, author) or end it — an advisory progress signal on a generating plan.

Correct a plan's OWN title and summary — the heading above the tree — without touching a single proposal.

Fill in a proposal you appended — the deepen turn while the plan is being written, or, with `revision: true`, a rewrite of a card on a plan already in review, in place.

Correct a proposal — including its parent, its dependency and supersedes edges, its obsolescence mark and note, and its whole repository axis (a repo, a row, a set, or a role) — even after the plan is in review; a corrected mark is re-checked, so setting one on an unfinished card is refused.

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