What it does
Render a task's plan of sub-steps for the user, laid out nicely. Returns (1) a formatted markdown checklist — progress bar, a you-vs-Claude split, and every step with its owner and status — which renders in any chat; (2) the same plan as structuredContent JSON; and (3) an interactive HTML widget with checkboxes for hosts that render MCP UI (it degrades to the markdown elsewhere). Call this after decompose_task/propose_plan, or whenever the user asks to see the plan. Each step's id is included so you can act on it with set_step_status / complete_task.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
task_id | string | Required | The parent task whose sub-steps make up the plan. |
Annotations
The hints the server sends with this tool. A host reads them to decide whether to ask you before a call.
- Read-only
readOnlyHint: true - Changes nothing.
- Destructive
destructiveHint: false - Only adds or reads; nothing already there is removed or overwritten.
- Idempotent
idempotentHint: — - Doesn't apply: the tool changes nothing.
- Open world
openWorldHint: false - Touches only your own Done account.
Which tokens can call it
A connection made with OAuth has full access. A token from Settings → Agent access → Extra MCP tokens can be narrowed, and a narrowed token never sees beyond its project or workspace.
- Full accessAllowed
- Read-only tokenAllowed
- Single-project tokenRefused
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Show me the plan for the move as a checklist.”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: