Taskwarrior MCP
Related Servers
Alternatives to Taskwarrior MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables multiple AI agents and IDEs to coordinate through a shared Markdown vault by delegating, claiming, and completing tasks and by writing and searching shared memory. It keeps the task dashboard synchronized while allowing safe cross-process access to the same workspace.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to read a task's live brief and update progress, checkpoint, hand off, create, and list tasks from within their own editor. A newly connected chat receives the current task state automatically, so work continues without re-explaining context.5Apache 2.0
- AlicenseAqualityCmaintenanceEnables a planning Claude chat and Claude Code to exchange work through local Markdown files, letting the chat create tasks that code agents pick up, complete, and report back on. Project-scoped task and report tools track each item's status from open through reported, eliminating manual copy-paste between the two clients.5MIT
- AlicenseNot gradedqualityAmaintenanceEnables structured multi-agent workflows by managing task claims, action logs, handoffs, and health-gated completion while keeping specifications as filesystem Markdown artifacts.29 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local multi-agent Codex collaboration through a SQLite task graph, atomic task claiming and leases, isolated Git worktrees, append-only events and messages, and a local web Kanban board.MIT
- FlicenseAqualityBmaintenanceEnables coding agents to track and coordinate project work through a shared SQLite ledger, including task plans, session ancestry, claims, work locations, blockers, and commits via MCP tools.9-
TDQS
Scored across 6 tools
Each tool targets a distinct aspect of task management: claim lifecycle, context dashboard, search/list, single-task detail, creation, and updates. The only mild overlap is between task_context (curated view) and task_list (search/filter), but descriptions clarify their different roles.
All tools use a consistent `task_` prefix and snake_case, with most following a verb_noun pattern (claim, list, get, create, update). `task_context` is a noun and slightly breaks the verb pattern, but the set remains highly predictable.
Six tools are well-scoped for a task management server with claim/handoff workflows. Each tool has a clear, non-redundant purpose, and the count is neither thin nor bloated.
The surface covers full task lifecycle (create, read, update, delete via status change) plus a sophisticated claim/handoff mechanism. Minor gaps exist, such as no explicit tool for adding/removing dependencies or managing tags, though task_update may accommodate some field changes.