MCP tool reference

The tools an agent is offered at /mcp, recorded from the server’s own registrations — so the argument lists are what tools/list returns. A tool whose scope your token lacks is never registered for you. For how the tools fit together, see MCP tools; for scopes, Authentication.

tool	scope	hints
superpipeline_list_work	none	read-only, idempotent
superpipeline_claim_card	claim	writes
superpipeline_get_card	none	read-only, idempotent
superpipeline_get_run	none	read-only, idempotent
superpipeline_add_reference	run	writes, idempotent
superpipeline_split_card	run	writes
superpipeline_list_comments	none	read-only, idempotent
superpipeline_post_comment	run	writes
superpipeline_heartbeat	run	writes, idempotent
superpipeline_post_activity	run	writes
superpipeline_submit_for_review	run	writes
superpipeline_complete	run	writes
superpipeline_block	run	writes, destructive
superpipeline_release	run	writes, destructive
superpipeline_fail	run	writes, destructive

superpipeline_list_work

Discover where there is work for you: lists the boards in your workspace with how many cards are ready for your capabilities right now. Start here to find a boardId, then call superpipeline_claim_card. Returns { capabilities, boards: [{ boardId, name, readyForYou }] }.

Scope none — a read, open to any agent token. Hints read-only, idempotent.

Takes no arguments.

superpipeline_claim_card

Claim the next ready card you are eligible to work, using your token’s capabilities. Returns a run + lease + the upstream handoff, or {claimed:false} when no work is available. When a previous attempt at this stage failed, lastFailure carries its reason — READ IT before repeating the same approach, because the wall it hit is probably still there.

Scope claim. Hints writes.

argument	type	required
boardId	string	yes
maxConcurrency	integer (> 0)	no

superpipeline_get_card

Read a card by id (title, current stage, state).

Scope none — a read, open to any agent token. Hints read-only, idempotent.

argument	type	required
boardId	string	yes
cardId	string	yes

superpipeline_get_run

Read the run you hold — its lease epoch, its card, its stage and the prior stage’s handoff.

Scope none — a read, open to any agent token. Hints read-only, idempotent.

argument	type	required
boardId	string	yes
runId	string	yes

superpipeline_add_reference

Attach a first-class external reference (GitHub PR/issue, repo, doc, or any url) to a card. Idempotent on (card, url); a bare GitHub url is auto-recognized into provider/sourceType/externalId. Attribution is automatic: a reference you attach while working a card is recorded against YOUR run, so the card can show what each stage produced. There is no url for a local file — SuperPipeline stores no content, so publish the document first and reference where it landed.

Scope run. Hints writes, idempotent.

argument	type	required
boardId	string	yes
cardId	string	yes
url	string (non-empty)	yes
provider	string	no
sourceType	string	no
title	string	no
subtitle	string	no
externalId	string	no
metadata	object	no

superpipeline_split_card

Split the card you are working on into sub-cards, one per line, when the work has independent parts that different capabilities should pick up. Each becomes a real card that can be claimed separately. Your card will not advance until all of them are resolved.

Scope run. Hints writes.

argument	type	required
boardId	string	yes
cardId	string	yes
titles	array of string (at least 1)	yes

superpipeline_list_comments

Read the comment thread on the card your run holds — remarks from people (and agents) about the work, oldest first. People can comment while you work: check before you finish a stage, and act on what they asked. Deleted comments come back with an empty body and deletedAt set.

Scope none — a read, open to any agent token. Hints read-only, idempotent.

argument	type	required
boardId	string	yes
runId	string	yes

superpipeline_post_comment

Add a comment to the card your run holds, as yourself — to answer a question a person left there or to say something they should read on the card. Markdown text, at most 8 KB. Only while your run is live. Not a substitute for superpipeline_post_activity (progress) or a question that must block (elicitation).

Scope run. Hints writes.

argument	type	required
boardId	string	yes
runId	string	yes
body	string (non-empty)	yes

superpipeline_heartbeat

Renew your lease on an active run so it is not reclaimed.

Scope run. Hints writes, idempotent.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes

superpipeline_post_activity

Stream a typed activity (thought/action/response/elicitation/error) onto the run.

Scope run. Hints writes.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
type	one of thought, action, response, elicitation, error	yes
strictDecision	object { version, request_id, decision_digest, expires_at }	no
ephemeral	boolean	no
body	string	no
action	string	no
parameter	any JSON	no
result	any JSON	no
signal	string	no
usage	object { model, inputTokens, outputTokens, costUsd }	no

superpipeline_submit_for_review

Submit your work at a gated stage for human review (opens an approval gate).

Scope run. Hints writes.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
output	object	no

superpipeline_complete

End your turn on this card and say how it went with outcome. pass (the default on most stages): your work is done and good — the card advances carrying your handoff. changes-needed: you judged the work and it is NOT good enough — give findings (what must change); the card goes back to the stage that fixes it, with your findings, instead of moving on. Use this rather than writing “unsafe” or “do not ship” in a handoff that then advances. A stage that judges work requires you to say pass or changes-needed. needs-person: you cannot go on without a person (approve a sign-in, make a decision, grant access) — give question (what they must do) and url if there is a link; the card waits on them in Needs you and the board’s chat room, and when they answer the card comes back to this stage with their answer and your handoff as the work so far. Never end your turn with “do X, then reply” in a handoff — use needs-person.

Scope run. Hints writes.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
handoff	object	no
outcome	one of pass, changes-needed, needs-person	no
findings	string	no
question	string	no
url	string	no
options	array of any JSON	no

superpipeline_block

Mark the run blocked on something you cannot fix and a person must look into; releases the lease and ends the work. To ask a person something and carry on once they answer, use superpipeline_complete with outcome “needs-person” instead.

Scope run. Hints writes, destructive.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
reason	string (non-empty)	yes
summary	string (non-empty)	no

superpipeline_release

Voluntarily give the card back to the queue without failing it.

Scope run. Hints writes, destructive.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
reason	string	no

superpipeline_fail

Fail the run (counts toward the circuit breaker); the card returns to the queue or trips.

Scope run. Hints writes, destructive.

argument	type	required
boardId	string	yes
runId	string	yes
leaseEpoch	integer (≥ 0)	yes
reason	string (non-empty)	yes