Developer Tools
donebear.com
A task manager that lets you assign tasks to an AI, which then produces pull requests, synced across devices.
ENDPOINT 1
https://mcp.donebear.com/mcp
MCP server metadata
- Name
- donebear
- Version
- 0.8.0
Done Bear is a GTD-style task manager. Tasks live in views: Inbox, Today, Upcoming, Anytime, Someday, Logbook (completed), and Trash (archived). get_context is orientation, not a warm-up. Call it when you need to resolve a project, label, team, or member by name, or when the user asks what is in their workspace, and skip it otherwise: going straight to the tool that answers the question is faster and the tools resolve names themselves. Pass the user's IANA timezone (e.g. Australia/Melbourne) to every tool that accepts it — Today and Upcoming are calendar-day dependent, and without a timezone the server resolves "today" in UTC. A new task goes to Today by default: task_add without a `when` schedules it for the caller's today. Pass `when: "inbox"` when the user is only capturing something. This makes the timezone matter on every create, not just on reads. Three things change that default when you do not state a `when`: no `timezone` and it lands in anytime, because today cannot be resolved; a `deadline` and it lands in anytime, because the work is due later rather than now; a `project` or `team` and it lands in inbox, because the task is already filed and should not also fill up Today. Dates are YYYY-MM-DD. Tasks use a workspace-scoped positive number in the `task` parameter, and every task write also takes `tasks` for up to 50 of them at once. Checklist item ids accept a full UUID or a prefix of 4+ characters; projects, teams, labels, and members also resolve by name. Failed lookups name the candidates, so read the error before retrying. The tools are shaped by what you are working on rather than by operation: `checklist`, `comment`, `attachment` and `project` each take an `action`, and `task_show` returns a task's checklist, labels and (via `include`) its comments and files. Confirm with the user before anything that touches many tasks at once or is hard to undo: a `tasks` array, archiving, removing a comment, and clearing fields. Call `guide` for the detail on a topic before working in it for the first time: - `views`: Placing a task in Inbox/Today/Upcoming/Anytime/Someday, reading a view, or working out why Today looks wrong. - `dates`: Setting or clearing a due date, or deciding between a deadline and a start date. - `editing`: Changing a task's fields, clearing a value, appending to notes, or moving a task between projects. - `bulk`: Completing, moving, or editing more than one task at a time, or sweeping a whole view. - `checklists`: Adding sub-steps to a task, building a list inside a task, or ticking items off. - `comments`: Discussing a task with teammates: reading its thread, replying, or correcting a comment. - `projects`: Deciding where a task belongs, creating a project or label, changing a project's status, or joining/leaving a project. - `search`: Looking a task up, listing a view, paging through results, or orienting in a new workspace. - `workspaces`: Working across multiple workspaces, hitting a permission or rate-limit error, or making retries safe. - `agents`: Starting work in a Done Bear workspace for the first time. - `importing`: The user asks how to move their tasks in from Todoist, Things, Trello or a CSV.
Known tools 15
guideRead Done Bear's guide for one topic: what the data means, how it relates to the rest of the product, and how to use it well.
Inferred read-onlyget_contextGet a snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member.
Inferred read-onlytask_showGet full details for a single task: its fields, labels and checklist items, by workspace-scoped task number.
Inferred read-onlytask_editUpdate fields on one task (`task`) or on several at once (`tasks`, max 50).
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.donebear]
url = "https://mcp.donebear.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"donebear": {
"type": "http",
"url": "https://mcp.donebear.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: donebear
Remote MCP URL: https://mcp.donebear.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"donebear": {
"url": "https://mcp.donebear.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"donebear": {
"type": "http",
"url": "https://mcp.donebear.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "donebear",
"transport": "streamable-http",
"url": "https://mcp.donebear.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for donebear.com was fetched 2026-08-10T23:19:26.406Z and is being refreshed.
donebear.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.