TaskWarrior MCP Server

What is TaskWarrior MCP Server?

A Node.js server implementing the Model Context Protocol (MCP) to enable AI assistants to interact with local TaskWarrior task management. It provides tools to view, add, and complete tasks, running the user's local task binary.

How to use TaskWarrior MCP Server?

Install globally with npm install -g mcp-server-taskwarrior, then add it to an MCP client such as Claude Desktop by editing claude_desktop_config.json to run npx -y mcp-server-taskwarrior. Ensure TaskWarrior is installed and configured on your system.

Key features of TaskWarrior MCP Server

• View all pending tasks
• Filter tasks by project and tags
• Add new tasks with description, due, priority, project, and tags
• Mark tasks as complete
• Runs local TaskWarrior binary

Use cases of TaskWarrior MCP Server

• Ask "What are my current work tasks?" to list tasks filtered by project.
• Add a high-priority task like "Call my sister" without switching terminals.
• Complete a task by telling the assistant "I've called my sister."

FAQ from TaskWarrior MCP Server

What prerequisites are needed?

TaskWarrior must be installed and configured on your system; this server runs the local task binary.

How do I install the server?

Run npm install -g mcp-server-taskwarrior from the command line.

How do I connect it with Claude Desktop?

Add a "taskwarrior" entry under mcpServers in claude_desktop_config.json with command: "npx" and args: ["-y", "mcp-server-taskwarrior"].

Does the server use stable task identifiers?

No. It currently uses the id field, which TaskWarrior renumbers when tasks are added or removed. Future versions plan to use the UUID instead.

What tools does the server expose?

Three tools: get_next_tasks (with optional project and tags filters), add_task (required description, optional due, priority, project, tags), and mark_task_done (required identifier – task ID or UUID).