What it does
Search the activity feed across every task you can see — comments, status changes and agent write-ups — instead of reading one task at a time. Use it to recall a past decision ("what did we decide about pricing"), a rejection reason, or whether an agent has already looked at something. Case-insensitive substring match on the entry body, newest first. Narrow further with task_id/author/kind/since; get_task still returns one task's full feed in order.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
q | string | Required | Case-insensitive substring match on the activity entry's body. |
task_id | string | Optional | Narrow to one task's feed. |
author | string | Optional | Who wrote the entry. Allowed values aleclaude |
kind | string | Optional | Entry type — see get_task's activity feed. Allowed values commentstatuscreated |
since | string | Optional | ISO timestamp — only entries after this. |
limit | integer | Optional | Maximum results (default 50).
|
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:
“What did we decide about pricing last month?”
Connect Done to your assistant
One MCP endpoint per account, over OAuth or a token. Step-by-step setup for each client: