Kanban MCP tools

The board’s MCP server (rev0 mcp, registered through mcp.json) gives an agent these tools. An agent sees each one as mcp__kanban__<name>, and the board must be running for any of them to work. To connect a client, see Connect an MCP client.

The kind column is the hint the server advertises to clients. It is advisory: what an agent may actually do is decided by the permission gate.

Tool	Kind	What it does
add_artifact	write	Register a deliverable you produced so it shows up in the ticket’s Artifacts section.
add_comment	write	Add a progress comment to a ticket’s activity timeline.
add_flow_plan	write	Submit your plan as a HIGH-LEVEL BEHAVIOR FLOW GRAPH instead of verbose prose.
add_knowledge_base_page	write	Propose a new Knowledge Base page (markdown) capturing something durable you learned that future agents and humans should reuse (a runbook, a gotcha, a convention).
add_plan	write	Submit your implementation plan (markdown).
add_spa_plan	write	Submit your plan as a self-contained INTERACTIVE HTML SPA instead of prose or a flow graph.
answer_subticket	write	Answer one or MANY of your own blocked subtickets in a single call.
approve_subticket_plan	write	Approve the plan of one of YOUR OWN subtickets, exactly as the human’s Approve button does: sets plan_approved and re-queues the child to build.
await_background_task	write	Start ONE long command and park on it immediately (start + await in one call).
await_background_tasks	write	Park this ticket until the named background tasks finish, then get RE-INVOKED.
await_subtickets	write	Wait for a set of your subtickets to finish, then get RE-INVOKED for synthesis (the N-child join).
check_background_tasks	read	Status, exit code and a short output tail for every background task, no parking.
claim_ticket	write	Claim a ticket to start working on it.
create_kb_space	write	Create a Knowledge Base SPACE: a top-level folder pages are filed into.
create_subticket	write	Create a subticket under a parent (ancestry must terminate at a human-created ticket, enforced server-side).
create_ticket	destructive	Create a NEW TOP-LEVEL ticket on the board.
delete_kb_page	destructive	PERMANENTLY delete a Knowledge Base page.
delete_kb_space	destructive	Delete a Knowledge Base space.
delete_ticket	destructive	PERMANENTLY delete a ticket and its history.
finish_ticket	write	Call this whenever you have FINISHED the work and nothing is blocking you, even if you would like a human to double-check it.
get_config	read	Read the board-wide settings (default model, max concurrent agents, repos root, the command allow/ask/deny lists, integration toggles, …).
get_goal	read	Read a Goal’s objective, iteration ledger and spend against its caps.
get_kb_page	read	Fetch one Knowledge Base page by id: its title, full markdown content, tags, and (for a ‘link’/‘external’ page) the external_url to WebFetch.
get_loop_digest	read	Read a Loop’s comprehension digest: a human-readable markdown summary of its pipeline (nodes + gate kinds), resource-cap usage vs limits, and recent Runs, so you can see at a glance what the Loop does and where it needs a human.
get_ticket	read	Get a single ticket including its description, mode, plan, tags, workdir and parent_id.
get_ticket_activity	read	Read the ticket’s activity timeline (comments, status changes, plans, system events), oldest first.
get_ticket_commits	read	List the ticket branch’s own commits with per-file +/- stats, newest first.
get_ticket_diff	read	Get the ticket branch’s code changes, parsed per-file for review.
get_ticket_tool_log	read	The ticket’s command/tool audit log: one structured entry per tool/command a prior agent run executed (tool, args, status, timing), derived from the transcript.
get_usage	read	Live Claude Code plan utilization (the 5-hour and 7-day rate-limit windows plus any extra credits) and an estimated dollar spend, the same data as the usage pill in the board’s top bar.
get_usage_phases	read	Average wall-clock a ticket spends in each status (in_progress, pending_action, in_review, …), derived from status-change timestamps.
get_usage_stats	read	Historical token-usage statistics for the board: tokens (input/ output/cache split), dollar cost, estimated water footprint (millilitres), models used, context-window occupancy and API latency, aggregated over time.
list_boards	read	List the boards on this instance (id, name, acronym, agents_enabled, color).
list_kb_pages	read	List Knowledge Base pages (id, title, slug, page_type, space_id, parent_id, …), optionally scoped to a space, board or parent page.
list_kb_spaces	read	List the Knowledge Base spaces (top-level wiki sections: id, name, …).
list_loop_templates	read	List the curated Loop pipeline templates available to instantiate via create_ticket(type=‘loop’, template_id=…): id, name, description, version, and declared params (name/required/default).
list_notifications	read	List the board’s notifications (ticket events surfaced to the human), newest first; pass unread_only=True for just the unread ones.
list_runs	read	List the past Runs (execution history) of a scheduled (cron) ticket, newest first.
list_subtickets	read	List the subtickets of a ticket: its direct children by default, or every descendant in the tree (recursive=True).
list_tags	read	List all tags already in use on the board, with usage counts.
list_tickets	read	List tickets, optionally filtered by status (backlog, todo, in_progress, pending_action, in_review, done, discarded), board_id and/or assignee.
log_chat	write	Append a chat/work-history message to the ticket (role e.g. assistant, user, tool).
merge_subticket	write	Land the branch of one of YOUR OWN subtickets.
merge_ticket	destructive	Merge a ticket’s branch into its base branch, on demand.
organize_kb_page	write	File an EXISTING Knowledge Base page into a space/parent, and optionally promote it out of quarantine into the live wiki.
post_review_findings	write	Post severity-graded code-review findings onto a ticket.
promote_all_kb_pages	write	Empty the Knowledge Base’s Pending review queue: take every quarantined agent proposal live at once.
propose_subtickets	write	PREVIEW the fan-out children you (an orchestrator) intend to dispatch, as STRUCTURED data, so the ticket detail shows a dedicated “agents to dispatch” panel the human reviews and edits before approving your plan.
reject_subticket_plan	write	Send the plan of one of YOUR OWN subtickets back for re-planning with notes, instead of correcting it yourself.
report_goal_progress	write	Report this iteration’s verdict on its Goal, then finish.
request_action	write	Use ONLY when you are BLOCKED mid-work and cannot continue without a human answer, decision, or manual step.
request_budget_increase	write	Call this when you are APPROACHING this ticket’s spend ceiling and need the human to decide whether to keep going.
resolve_loop_gate	write	Act on a FAILED adversarial review in a Loop pipeline you dispatched.
resolve_review_comment	write	Mark ONE inline diff-review comment resolved once you have addressed it.
resolve_subticket_permission	write	Allow or deny a permission request one of YOUR OWN subtickets is parked on.
resume_loop_run	write	Hand a Loop Run back to its pipeline after talking with the human.
return_subticket	write	Send finished subtickets BACK for another turn, with advice.
revert_ticket	destructive	Revert a previously-merged ticket’s branch out of its base branch.
revise_subticket_plan	write	Replace/correct the plan of one of YOUR OWN subtickets before approving it, when you are not happy with what the child produced.
run_loop_now	write	Fire ONE run of a Loop ticket right now, regardless of its schedule.
search_knowledge_base	read	Search the team Knowledge Base (the board’s shared wiki) for docs, runbooks, conventions, decisions and saved links relevant to your ticket.
send_ticket_message	write	Send one durable message from this ticket to another agent ticket.
set_branch	destructive	Rename / re-choose THIS ticket’s working branch mid-run.
set_plugin_source	destructive	Load, unload or remove an external plugin source, with permission.
set_repo_binding	destructive	Re-point a ticket’s git address: repository, base branch, working branch and worktree, validated and written together.
set_verification_checks	write	Define the ticket’s minimum VERIFICATION CHECKS: the tests / conditions / goals the human confirms with the plan and that you cannot bypass to complete the ticket.
start_background_task	write	Start a LONG shell command on the board and KEEP WORKING.
stop_background_task	write	Kill one running background task (its whole process group).
tag_ticket	write	Tag a ticket.
terminal	write	Type into this ticket’s SHARED terminal, then read its screen.
update_kb_page	write	Edit an EXISTING Knowledge Base page’s title, content or tags.
update_kb_space	write	Rename, re-describe, re-order or archive a Knowledge Base space.
update_loop_pipeline	write	Replace a Loop ticket’s pipeline, the executable DAG it runs each fire, with a new graph.
update_status	write	Set a ticket’s status explicitly: backlog, todo, in_progress, pending_action, in_review, done, discarded.
update_ticket	write	Edit a ticket’s editable fields.