Repository avatar
Other Tools
v0.1.0
active

taskden

io.github.CloudCorpRecords/taskden

DoneBear task workspace over MCP: tasks, projects, checklists, comments and labels.

Documentation

taskden

Your DoneBear workspace, reachable from any MCP client. taskden is a local forwarding client for the hosted DoneBear MCP service: it answers tools/list on your own machine from the captured tool definitions and forwards every call to DoneBear, returning the results exactly as the service sends them back.

The surface is a personal task workspace: tasks with views and due dates, projects, checklists, comments, attachments and labels, plus a guide tool and a workspace-context snapshot. Nothing is cached, stored or computed locally — the package is a pipe, not a database.

The tools

  • guide — Read DoneBear's guide for one topic: what the data means and how it relates to the rest of the product. Requires topic and context.
  • get_context — A snapshot of the current workspace: task counts per view, recent open tasks, and every project, label, team and member. Requires context.
  • task_list — List tasks in the workspace, most recently updated first. Requires context.
  • task_show — Full details for a single task: fields, labels and checklist items, by workspace-scoped task number. Requires task and context.
  • task_add — Create a new task, with placement (when: today, inbox, upcoming, anytime, someday), project, labels and more. Requires title and context.
  • task_edit — Update fields on one task, or on several at once (max 50). Only the provided fields change. Requires context.
  • task_agent_get — Read the task-agent identity bound to this connection's existing API key in one workspace. Requires workspace_id and context.
  • task_agent_register — Explicitly register one assignable task agent for this connection's existing key in one workspace. Creates no key and changes no scope. Requires expected_key_id, name, workspace_id and context.
  • task_done — Mark a task complete, or several at once (max 50); they move to the Logbook view. Requires context.
  • task_reopen — Reopen a completed task, or several at once (max 50). Requires context.
  • task_archive — Archive a task, or several at once (max 50); they move to the Trash view. Requires context.
  • project — Create or change a project (action: "add" or "edit"). Requires action and context.
  • search — Ranked lexical search over task titles and descriptions across the workspace. Requires query and context.
  • checklist — Change the checklist on a task: add, check, uncheck or remove items. Requires action, task and context.
  • comment — Write on a task's comment thread. Requires action, task and context.
  • attachment — Add a file to a task from an HTTPS URL, or remove one. Requires action, task and context.
  • label_create — Create a new label in the workspace and return its id. Requires title and context.

Every tool takes a context argument: the workspace context string the DoneBear service uses to scope the call.

Install and run

As an MCP server via npm:

npx -y @reneturcios/taskden mcp

MCP client configuration:

{
  "mcpServers": {
    "taskden": {
      "command": "npx",
      "args": ["-y", "@reneturcios/taskden", "mcp"]
    }
  }
}

As a container:

docker run -i ghcr.io/cloudcorprecords/taskden
docker run --rm ghcr.io/cloudcorprecords/taskden task_list '{"context":"..."}'

CLI

One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:

taskden get_context '{"context":"..."}'
taskden task_add '{"title":"Water the plants","context":"..."}'
taskden search '{"query":"invoice","context":"..."}'
taskden --version

Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.

Configuration

  • DONEBEAR_MCP_URL — Overrides the upstream endpoint. The default is the pinned hosted endpoint, https://mcp.donebear.com/mcp. (The override variable is a reconstruction added by this rebuild.)

The DoneBear registry record declares no headers on its remote, so taskden never sends an Authorization header — or any other credential — upstream. The tool surface was captured keyless.

Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with taskden error:.

How forwarding works

The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.

Development

npm install
npm run build   # tsc -> dist/ (dist/cli.js is the bin)
npm test        # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev     # run the CLI from source

The test suite checks the served tool list against the captured surface (all 17 tools, deep-equal, in order), exercises the session handshake and its reuse, covers the endpoint override, asserts that no Authorization header is ever sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.

License

MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.

NPM
@reneturcios/taskden
Install Command
npm install @reneturcios/taskden
Runtime: npx
OCI
ghcr.io/cloudcorprecords/taskden:0.1.0
Install Command
docker pull ghcr.io/cloudcorprecords/taskden:0.1.0:undefined
Runtime: docker