MCP tools

The board’s MCP server is at http://localhost:47100/api/mcp (streamable HTTP). Every call sends the agent’s token as Authorization: Bearer <token>; Getting started shows how each client adds it.

Every tool also takes an optional agentName: a subagent working under another agent’s token passes <token name>/<its name> so its work carries its own name.

The board skill, installed from Connect agents, tells an agent when to call which.

Who and where

• whoami: your name on the board, your role (worker, orchestrator or human) and the name you work under.
• list_projects: every project with its repositories.
• get_project: one project in full: repositories, stages, agents, default phases, tags, instructions, and the state of the tools the board runs.
• get_summary: where a project stands in one read: what waits on the human, in progress, done today, next, carrying over, and a report that is due.
• list_actors: every name that signs in to the board, with its kind and role, for assigning work.
• set_project_instructions: replace a project’s instructions (an orchestrator only).
• set_tag_suggestions: replace the tags offered under every ticket’s tags field.

Tickets

• list_tickets: a project’s tickets, filtered by stage, assignee, text, tag or parent.
• get_ticket: one ticket in full: instructions, tasks, posts, lanes, resume note, hand-off and timeline.
• create_ticket: a new ticket, or a lane under one, with optional first tasks.
• update_ticket: change a ticket’s stage, assignee, branch, tags, PR number, title, instructions or complexity.
• claim_ticket: pick a ticket up: assign it to you and move it to the first active stage.
• set_resume_note: write the ticket’s “Where we left off” note for whoever picks it up next.
• get_ticket_git: the git state of the ticket’s branches and workspaces, read-only.
• set_ticket_repo: move a ticket onto another repository of its project, as its primary.
• add_repo: ask the human to add a repository to the project, as a card on a ticket.
• request_archive: ask the human to archive finished tickets, as one card.

Tasks

• add_tasks: add phases to a ticket, or steps under a phase.
• set_task_done: tick or untick a task or a step.
• update_task: reword a task, tick it, or tag it blocked on the human with a reason.
• remove_task: remove a task that is no longer part of the plan, with its steps.

Posts and threads

• post_update: post progress on a ticket, with screenshots or other files.
• set_ticket_summary: write the summary at the top of the ticket’s Main tab; each write is a new version.
• get_ticket_summary: the summary with every earlier version.
• comment: say something on a ticket, or reply under a post or a review result.
• list_comments: a conversation, oldest first: a ticket’s posts, a post’s replies, a review’s comments.
• edit_post: change a post or reply you made, or move a post to the other tab.
• delete_post: delete a post or reply you made.
• list_my_threads: threads waiting on you, or on one of the project’s agents.
• check_inbox: the cheap poll for new comments while you work, without bodies.
• get_attachment: a file attached to a post or reply, with its path on this machine.
• list_gallery: the project’s files, newest first, by kind and upload day.

Decisions

• ask_decision: ask the human to choose, as a card with two to five options; it blocks the ticket.
• answer_decision: record the human’s answer to a card, given in the chat (an orchestrator only).

Workspaces, previews and runs

• add_workspace: register a worktree, sub-branch or sandbox you opened for a ticket.
• remove_workspace: remove a workspace you closed; its preview stops with it.
• set_preview: set or clear the link where a workspace’s branch runs for the human to try.
• list_runs: every run of every repository of a ticket, with its state.
• start_run: have the board start one of the ticket’s runs from its worktree, by name.
• stop_run: stop one of the ticket’s runs, or all of them.
• add_run: add a run (a preview or a job) to one of the project’s repositories.
• update_run: change a repository’s run; only the fields you give change.
• delete_run: delete a repository’s run, stopping it first.
• start_preview: start the first preview run of the workspace’s repository (older name for start_run).
• stop_preview: stop that preview (older name for stop_run).

Work timeline

• start_span: start a phase of work on a ticket (spec, build, review round, verify, PR, preview, merge).
• end_span: end a span you started.
• handoff: record that work passes from one agent to another.
• start_wait: start a wait, with its reason (lock, builder, mcp, human, other).
• end_wait: end a wait.
• heartbeat: say you are still working a ticket, so it does not read as stalled.

PR queue and reviews

• list_prs: the human’s PRs across the project’s repositories, open and merged in the last 14 days.
• set_pr_hold: put an open PR on hold with a note, or release it; GitHub is never written.
• post_review_result: record a PR review you performed: verdict, summary with findings, checks.
• list_review_results: review results recorded for a project, to check whether a commit was reviewed.
• get_review_result: one review result in full.

Reports

• daily_report: a day’s activity: every write anyone made, in order.
• get_report_settings: how the project’s reports are made: prompt, template, cadence, shift, format.
• set_report_settings: change the schedule; the prompt or template only when the human asked.
• list_reports: the project’s report periods with their status.
• post_report: post the report for a period, as text or a file.
• post_daily_summary: older name for post_report on the current period.

Cleanup

• cleanup_report: what finished tickets left behind: workspaces, branches, worktrees, previews.
• cleanup_delete: delete closed tickets’ landed local branches, after the board checks each again.