Claude task manager: connect Claude to your to-do list over MCP

"Claude task manager" usually means one specific thing: can Claude actually read, update, and finish the things on your list, not just chat about them. With Done, the answer is yes. Connect Claude once over MCP, and it can pull its queue, claim a task, do the work, and report back into the same task you're looking at — scoped to your account and nothing else.

Two ways to connect Claude

Done is a full OAuth 2.1 authorization server for its own MCP endpoint, so claude.ai and Claude Desktop can add it as a custom connector and handle authentication themselves — there's no token to copy or store. If you're wiring up Claude Code or a script instead, generate a per-account bearer token from the Account panel and set it once in your MCP client config.

• claude.ai or Claude Desktop: Settings → Connectors → Add custom connector → paste https://trydone.app/mcp → Connect. Claude discovers Done's OAuth endpoints, registers itself, and sends you to Done to sign in and approve access.
• Claude Code or a custom script: generate a token from the Account panel, then point your MCP client config at https://trydone.app/mcp with an Authorization: Bearer header.
• Either way, the connection is scoped to your account alone — there's no shared or global token Claude, or anyone else, could reuse across accounts.

What Claude can actually do once connected

Once connected, Claude gets the same set of workflow-shaped tools regardless of whether claude.ai, Claude Desktop, or Claude Code is driving it — not raw database CRUD, but actions that mirror how you'd actually work a task yourself: pull the ready queue, claim one, comment progress, and either complete it or propose completion for your approval.

• list_my_tasks / next_task — see or atomically claim the top of Claude's queue, so a fleet of agents never grabs the same task twice.
• get_task — load one task's full context: notes, subtasks, blockers, and the whole activity feed.
• comment_on_task — post progress or results in markdown, right where you'll see them next to the task.
• complete_task or propose_completion — close a task directly if it's marked auto-OK, or post a summary and wait for your approval if it isn't.
• decompose_task and propose_plan — break a big task into subtasks, or lay out a plan before doing the work, for anything too large to just start on cold.

A typical Claude session

A run looks roughly the same every time. Claude calls get_digest for what's overdue and due today, then list_my_tasks or next_task to find the top of its queue. It loads the task with get_task, reads any notes_for_agent and the acceptance_criteria — the concrete bar its result gets checked against, not just instructions — then does the work and checks it against that bar before calling complete_task or propose_completion.

Running Claude on a schedule

Done doesn't reach out and start a run on its own — it's a queue, not a scheduler, and nothing happens until some client asks. With Claude Code, you can set up a Routine that polls on whatever cadence fits you: every morning, every hour, once a night. Claude checks the queue each time, proposes plans for anything substantial, and works through whatever you've already approved since the last run.

Keeping Claude on a leash

You control how much Claude can do without asking, and none of it depends on trusting the model more or less. Scope its token to read-only or a single project (a Pro/Teams feature) if you want it to observe, or work in one place only. Mark only the tasks you're genuinely comfortable auto-closing as auto-OK; everything else routes through propose_completion and sits in your Control Room until you look at it. And every session runs as an auditable run with its own tool-call and time budget, so a session can't quietly keep going long after you've stopped watching it.