What it does
Pull just what changed since your last session, instead of re-reading the whole board on every run. Call with no cursor the first time — that anchors a cursor and returns no deltas (so a first call can never dump the whole board's history); store the returned cursor and pass it back on your next call to get everything that happened in between. Task changes cover status, assignment and plan approval (whatever bumps a task's updated_at); activity covers comments, status notes and agent write-ups. Triggers (@claude mentions, "Run now") are NOT included — call list_triggers for those, and check it first regardless, since a request outranks ordinary queue order. When has_more is true the activity page was full: call again straight away with the returned cursor to read the rest. An invalid or stale cursor just re-anchors to now rather than erroring.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
cursor | string | Optional | The cursor returned by your previous changes_since call. Omit on first use. |
limit | integer | Optional | Maximum activity entries to return (default 50). Task changes aren't capped by this.
|
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:
“What's changed on the board since your last session?”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: