What it does
Get one task in full: notes, metadata, subtasks, any calendar events it's tied to, and the activity feed (comments + status history, each entry naming who wrote it). Call before working a task to load context the human left.
CONTEXT BUDGET: the activity feed returns the NEWEST 50 entries by default. Use limit (0–500) to change that, and include to ask for only the sections you need. Whenever anything is left out, the response carries context_summary saying exactly what — how many older entries exist and which sections you didn't request — so a short payload is never mistaken for a complete history. If it is absent, you have everything. When it says entries were omitted, reach for search_activity rather than assuming; do not infer that a task has no earlier history from a feed that was windowed.
It also resolves all three tiers of the human's standing instructions to you, so you read them in the same call that loads the work: workspace_brief (everything in this workspace), project_brief (everything in this project), and the task's own notes_for_agent. PRECEDENCE: workspace → project → task, most specific last. They are additive context, not a chain where one replaces another — read all three. Where two genuinely conflict, the narrower one is a more recent decision about narrower ground, so it wins: the task's note beats the project brief, which beats the workspace brief. All three are one-way, from the human to you; reply with comment_on_task, or propose new wording for the project or task brief with propose_brief_edit (ask_decision for the workspace one). A task that was sent back and has no brief proposal off it yet carries a one-line brief_hint saying so.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | Required | |
include | string[] | Optional | Which optional sections to load. Omit for all of them. The task itself and all three standing briefs are always returned — they are the human's instructions to you, not an optional section. Allowed values subtasksblockerstagsactivityrunsdecisionscalendar |
limit | integer | Optional | Newest activity entries to return (default 50). 0 returns the counts without the entries.
|
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 tokenAllowed
- Single-workspace tokenAllowed
Try it
With Done connected, ask your assistant something like:
“Open the launch checklist task and read everything I left on it.”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: