Loading...
MCP server for TaskWarrior, enabling task management (view, add, complete) via natural language, but relies on local TaskWarrior install and unstable task IDs.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
MCP server for TaskWarrior, enabling task management (view, add, complete) via natural language, but relies on local TaskWarrior install and unstable task IDs.
This server provides a convenient interface to TaskWarrior, but its reliance on local execution and unstable IDs introduces moderate risks. It's relatively safe for personal use, but caution is advised when integrating it into more complex or shared environments.
Performance is likely limited by the speed of the local task binary and the size of the TaskWarrior task list. Large task lists may result in slower response times.
No direct cost, as it uses a local TaskWarrior installation. However, consider the cost of maintaining the TaskWarrior configuration and any associated infrastructure.
npm install -g mcp-server-taskwarrior{
"mcpServers": {
"taskwarrior": {
"command": "npx",
"args": [
"-y",
"mcp-server-taskwarrior"
]
}
}
}get_next_tasksRetrieves a list of pending tasks, optionally filtered by project and tags.
Read-only operation, no modification of data.
add_taskAdds a new task to TaskWarrior with a description, due date, priority, project, and tags.
Adds new data, but does not modify existing tasks.
mark_task_doneMarks a task as completed using its ID or UUID.
Modifies the state of a task, but is generally non-destructive.
None
This server provides a convenient interface to TaskWarrior, but its reliance on local execution and unstable IDs introduces moderate risks. It's relatively safe for personal use, but caution is advised when integrating it into more complex or shared environments.
Autonomy is limited by the capabilities of the underlying TaskWarrior installation and the potential for unstable task IDs.
Production Tip
Implement robust input validation and error handling to prevent unexpected behavior and potential security issues.
No, this server does not have built-in authentication. It relies on the security of the local TaskWarrior installation.
No, this server only works with a local TaskWarrior installation.
The wrong task may be marked as done. This is a known issue due to the unstable nature of TaskWarrior task IDs. UUIDs should be used instead.
The server uses the default TaskWarrior configuration. You may need to adjust your system's environment variables to point to a different configuration file.
If TaskWarrior supports recurring tasks, then it should be possible to add them using the `add_task` tool with the appropriate parameters.
If TaskWarrior supports task dependencies, then it should be possible to manage them using the `add_task` tool with the appropriate parameters.
Since there is no authentication, ensure that the server is only accessible on a trusted local network and that the TaskWarrior configuration is properly secured.