Get the FREE Ultimate OpenClaw Setup Guide →

mcp -taskwarrior

MCP Server for TaskWarrior!

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio awwaiid-mcp-server-taskwarrior npx -y mcp-server-taskwarrior

How to use

This MCP server provides a bridge between the MCP protocol and the TaskWarrior command-line tool. It exposes three tools: get_next_tasks to list all pending tasks with optional filtering by project or tags; add_task to create a new TaskWarrior item with required and optional fields such as description, due date, priority, project, and tags; and mark_task_done to mark a specific task as completed using its identifier. The server runs locally and relies on your installed TaskWarrior binary, so you must have TaskWarrior configured on your system for the MCP server to function correctly.

To use the tools, connect to the MCP endpoint and call get_next_tasks with any desired filters, or call add_task with a task description and optional fields like due, priority, project, and tags. When you’re ready to complete work, use mark_task_done with the task’s identifier (or UUID, when supported). This setup allows you to automate task management workflows from your preferred interface while delegating actual task storage and execution to TaskWarrior.

How to install

Prerequisites:

  • Node.js and npm installed
  • TaskWarrior installed and configured on your system (the 'task' command should be available in your PATH)

Installation steps:

  1. Install the MCP server package globally
npm install -g mcp-server-taskwarrior
  1. Verify Node.js and task binary are accessible
node -v
task --version
  1. Run the MCP server using npx as defined in the configuration (or install locally and run with the provided command)
# If using the README example configuration
npx -y mcp-server-taskwarrior
  1. If you’re integrating with Claude Desktop or another client, configure the MCP connection to point at the running server (see your client’s MCP configuration docs).

Additional notes

Notes and tips:

  • The server currently identifies tasks by TaskWarrior IDs, which can be unstable if tasks are renumbered. UUID support may be added in the future.
  • Ensure the 'task' binary is installed and accessible in the environment where the MCP server runs.
  • If running behind a firewall or on a non-default port, configure your client to connect to the correct endpoint and port.
  • The npm package name is mcp-server-taskwarrior; use the provided npx command to fetch and run the server as shown in the usage example.

Related MCP Servers

Sponsor this space

Reach thousands of developers