Planban MCP tools reference

Planban's MCP server exposes 13 tools by default for reading boards, changing Items and opening the board, and seven more administration, recovery and legacy tools only when the PLANBAN_MCP_PROFILE environment variable asks for them.

The server runs locally over stdio. Codex and Claude Code start it through the Planban plugin; other hosts start it directly, as described in Use Planban from other MCP hosts. Hosts may add their own prefix to the tool names, but each name ends in planban_<operation>.

Which tools are available by default?

ToolWhat it does
planban_statusChecks whether Planban is set up for a repository and reports its live state paths
planban_list_boardsLists the boards registered on this device
planban_get_boardLoads one board: its project, columns, revision and every card
planban_query_cardsSearches and filters cards without changing anything
planban_get_cardReads one card, with its document paths, metadata and owning Group
planban_read_docReads a card's Spec or Plan
planban_create_cardCreates an Item, with optional placement, tags, metadata, Spec and Plan
planban_create_cardsCreates several sibling Items in one change, optionally inside a Group
planban_create_groupCreates a Group and places existing Main Board Items inside it
planban_move_cardChanges an Item's Status, ownership or position in one change
planban_update_cardChanges fields other than Status: title, summary, next action, tags, blocked-by, metadata
planban_write_docReplaces a card's Spec or Plan, with optional stale-file protection
planban_launch_boardStarts or finds the local board app and returns a verified board URL

What does each tool take and return?

Every tool except planban_list_boards also needs the board: cwd, the absolute path of a set-up repository, or repoId, a registered board id, used only when cwd is absent. The table lists the other inputs. Tools that change Items accept an optional baseRevision and refuse the change if the board has moved on.

ToolRequired inputsOptional inputs
planban_status
planban_list_boardsincludeArchived
planban_get_board
planban_query_cardssearch, projection (main, group, flattened), groupId, hierarchyScope (projection, root, owned, leaf, selected-group), groupRole (any, group, item-only), statuses, blocked (any, blocked, unblocked), tags
planban_get_cardcardId
planban_read_doccardId, kind (spec or plan)
planban_create_cardtitlestatus (default pending), summary, nextAction, tags, metadata, specMarkdown, planMarkdown, position (top, bottom), afterId, parentId, baseRevision
planban_create_cardstitlesstatus (default pending), parentId, baseRevision
planban_create_grouptitlesummary (the Group objective), nextAction, status, itemIds, anchorId, specMarkdown, planMarkdown, baseRevision
planban_move_cardcardId, and one of status, parentId, afterIdbaseRevision, completionConfirmed
planban_update_cardcardIdtitle, summary, nextAction, tags, blockedBy, metadata, baseRevision
planban_write_doccardId, kind, markdownexpectedMtimeMs
planban_launch_boarddemo (then no board is needed), port (default 4317)

A few rules the tools enforce:

  • planban_create_card writes a default Spec when specMarkdown is omitted, and creates a Plan only when planMarkdown is supplied.
  • planban_move_card takes parentId: null for the Main Board and afterId: null for the first position. A move to complete requires completionConfirmed: true. A Group cannot be placed inside a Group.
  • planban_update_card clears summary, nextAction, blockedBy or metadata when given null, and replaces the whole tag list when given tags.
  • planban_write_doc replaces the whole document. With expectedMtimeMs set to the mtimeMs from the last read, it refuses to overwrite a newer file.
  • planban_launch_board with demo: true creates or reuses the Planban Demo board. If another program holds the port, it fails with Port 4317 is already in use by another service.

Each tool returns a one-line text summary and the full data as structured content. A change returns the board summary with itemCount and the changed card, rather than every card; planban_get_board remains the full read. A failed call returns an error whose message says what was wrong, such as Card not found: <id>.

What does every result include?

Results that concern one board carry a board link. This covers planban_status for a set-up project, planban_get_board, and every tool that creates or changes Items or documents:

FieldMeaning
boardUrlThe board's URL, such as http://127.0.0.1:4317/boards/<repo-id>
boardUrlVerifiedtrue when the local app answered a health check for this board
userReplyA ready-made link for the agent's reply: url, markdown and urlRequired: true

When the URL is verified, userReply.markdown reads [Open the verified board](URL). When it is not, it reads [Open the board](URL) and userReply.verifyWith names planban_launch_board. These results never start the app themselves.

planban_launch_board returns url, urlVerified: true, serviceReady: true, started (whether it started the app or reused a running one), and the same userReply.

Which tools only read?

planban_status, planban_list_boards, planban_get_board, planban_query_cards, planban_get_card and planban_read_doc are marked read-only. The others change a board, except planban_launch_board, which changes no board but can start the local app. No default tool is marked destructive.

How do I enable the administration and recovery tools?

Set PLANBAN_MCP_PROFILE in the MCP server's environment to one or more of these profile names, separated by commas:

ProfileAdds
adminplanban_archive_board, planban_restore_board, planban_duplicate_board, planban_delete_board
maintenanceplanban_export_flat_v1, planban_reconstruct_hierarchy
legacyplanban_set_card_parent, the older form of moving an Item into or out of a Group
fullEvery tool above

planban_delete_board needs confirmRepoId to match repoId exactly. Before it deletes the board's planning state, it copies it to a timestamped backup under ~/.planban/backups/boards/. It never deletes your project repository. These tools match the CLI's board and recovery commands.

What instructions does the server give the agent?

When a host connects, the server sends instructions that every agent receives, with or without the Planban skills. They tell the agent to:

  • prefer the Planban tools for all board, card and document reads and writes;
  • pass cwd as the absolute repository path, or repoId for a registered board;
  • read .planban/agent-context.md before creating or materially editing owner-facing content, and follow the Planban protocol and house style when installed;
  • make one change at a time on each board;
  • move cards to Complete only when you ask, confirm review or testing, or waive review;
  • use planban_move_card for all placement;
  • include the exact clickable board URL from userReply.markdown after opening the board or finishing a batch of changes;
  • make at most one attempt to show the board in an in-app browser, and never reopen it after every write;
  • call planban_launch_board once when boardUrlVerified is false.