Modify Kanban Card
kanban.cardAdd, move, or toggle Kanban cards. Automatically creates missing columns. Supports optional due dates and positions. Returns a mutation envelope with change details.
Instructions
Add, move, or toggle a card on a Kanban board. The op field selects the mutation and determines which other fields are required: add needs columnName and cardText (plus optional status, dueDate, position); move needs cardText, fromColumn, toColumn (plus optional position); toggle needs cardText (plus optional columnName to scope the search). Missing destination columns are created automatically. Returns a {changed, target, summary, ...} mutation envelope.
Operates on the session-active vault (see vault.current — selectable via vault.select) unless an explicit vaultPath argument is passed, which always wins.
Examples:
Example 1 — Add a new card to the Todo column with a due date:
{
"op": "add",
"filePath": "Boards/Project.md",
"columnName": "Todo",
"cardText": "Write migration doc",
"dueDate": "2026-05-01",
"position": "end"
}Example 2 — Move a card from In Progress to Done:
{
"op": "move",
"filePath": "Boards/Project.md",
"cardText": "Write migration doc",
"fromColumn": "In Progress",
"toColumn": "Done"
}Example 3 — Toggle a card's completion in any column:
{
"op": "toggle",
"filePath": "Boards/Project.md",
"cardText": "Write migration doc"
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| changed | Yes | True if the tool altered vault state on this call; false if it was a no-op. | |
| target | Yes | The path or identifier the tool acted on. | |
| summary | Yes | Short human-readable summary of what happened. |