Taskwarrior MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| taskwarrior_listA | |
| taskwarrior_addA | |
| taskwarrior_completeA | |
| taskwarrior_modifyA | |
| taskwarrior_deleteA | |
| taskwarrior_getA | |
| taskwarrior_annotateA | |
| taskwarrior_startA | |
| taskwarrior_stopA | |
| taskwarrior_projectsA | |
| taskwarrior_tagsA | |
| taskwarrior_undoA | |
| taskwarrior_summaryA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose targeting specific operations in Taskwarrior's task management lifecycle. Tools like add, modify, complete, delete, start, and stop handle different states and actions without overlap, while list, get, projects, tags, summary, and annotate serve distinct informational roles. The descriptions reinforce these boundaries, making tool selection unambiguous.
All tool names follow a consistent 'taskwarrior_' prefix with a descriptive verb_noun pattern (e.g., taskwarrior_add, taskwarrior_list, taskwarrior_modify). This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the 13 tools.
With 13 tools, this server is well-scoped for managing tasks in Taskwarrior, covering core CRUD operations (add, get, modify, delete), lifecycle states (start, stop, complete), informational queries (list, projects, tags, summary), and utilities (annotate, undo). Each tool earns its place without bloat, aligning with the domain's complexity.
The tool set provides complete coverage for Taskwarrior's domain, including task creation, retrieval, updating, deletion, state management (start/stop/complete), filtering, metadata access (projects/tags), annotations, undo functionality, and summary statistics. No obvious gaps exist; agents can perform all essential workflows without dead ends.