get_next_tasksLABSCO SUMMARY
Your real task list, in the conversation you were already having.
Because it drives the local task binary, everything lands in the same database your terminal uses. The author flags one thing worth knowing: completion currently goes through TaskWarrior's task id, which gets renumbered as tasks are added and removed, so pass the UUID when you are acting on something you looked up earlier.
What it is
A Node.js server that runs your local TaskWarrior installation: pending tasks, new tasks and completion.
What you get
- All pending tasks, optionally filtered by project or by one or more tags (get_next_tasks)
- A new task with description, due date, priority of H, M or L, project and tags (add_task)
- A task marked complete by id or UUID (mark_task_done)
Requirements
TaskWarrior installed and configured, since the server runs your local task binary. Installed globally from npm as mcp-server-taskwarrior, or run with npx.
Setup effort
One command — npx -y mcp-server-taskwarrior
USE CASES
Finding out what you should be working on
List the pending tasks and read them in priority order.
Capturing a task the moment it comes up
Add it with a due date, priority and project while you are still talking about it.
Closing out something you have finished
Mark it done by UUID, so a renumbered id does not close the wrong task.
Reviewing one project's open work
Filter the pending list by project or tag rather than reading the whole backlog.
3 tools
Listed in project docs. Your client may show a different list.
add_taskmark_task_doneBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation. The server needs the TaskWarrior task binary installed to start.
Requires
npx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npx -y mcp-server-taskwarriorMCP Clients
Claude Desktop
{
"mcpServers": {
"taskwarrior": {
"command": "npx",
"args": [
"-y",
"mcp-server-taskwarrior"
]
}
}
}