tasker-mcp

CLI and local MCP server for Tasker — a personal daily task tracker where unfinished tasks spill over to today. Drive your board from the terminal or from an agent like Claude Code, over the same tasker.json the web app syncs to, so all three stay in sync.

This package ships two binaries: tasker (the CLI) and tasker-mcp (the stdio MCP server). Both bundle their dependencies — no install footprint beyond the package itself.

The data file

Everything reads/writes one JSON file, resolved in this order:

1. --file <path> (CLI only)
2. $TASKER_FILE
3. ~/Tasker/tasker.json — the shared default (auto-created)

Point the web app's folder sync at the same folder and the app, CLI, and MCP are one board. Writes are atomic; the web app picks up external edits live.

CLI

npm i -g tasker-mcp                 # installs the `tasker` command (and `tasker-mcp`)
export TASKER_FILE=~/Tasker/tasker.json

tasker add "Fix KF4-12461" --priority high --when tomorrow
tasker ls                           # today's board (add --json for machine output)
tasker done 1                       # by index, short id, or full id
tasker sub add 1 "Write tests"
tasker ws add "Personal"            # workspaces: ws ls / add / switch / rename / rm
tasker report --range 7
tasker help

Every command accepts --json; errors go to stderr with a non-zero exit code; nothing prompts.

Claude Code (MCP)

claude mcp add tasker -s user -- npx -y tasker-mcp

-s user registers it for every project. It reads ~/Tasker/tasker.json by default; for another folder, append -e TASKER_FILE=/full/path/to/tasker.json.

Then ask Claude: “add ‘review the Q3 doc’ to my Work board, high priority.” The MCP server runs locally on your machine and reads the same file — nothing is hosted. Tools exposed: list_tasks, add_task, complete_task, reopen_task, update_task, move_task, delete_task, add_subtask, toggle_subtask, update_subtask, delete_subtask, list_workspaces, create_workspace, switch_workspace, rename_workspace, report.

License

MIT