Taskwarrior MCP Server

MCP server for taskwarrior

Local serverstdio

What is the Taskwarrior MCP server?

Taskwarrior becomes available to MCP clients through the taskwarrior mcp server. MCP server for taskwarrior.

What Taskwarrior does

Node.js server implementing Model Context Protocol (MCP) for TaskWarrior operations.

Key capabilities

  • View pending tasks
  • Filter tasks by project and tags
  • Add new tasks with descriptions, due dates, priorities, projects and tags
  • Mark tasks as complete

Tools it exposes

Once connected, the assistant can call these 11 tools directly:

  • get_next_tasks — Get a list of all pending tasks
  • project — Filter by project name
  • tags — Filter by one or more tags
  • add_task — Add a new task to TaskWarrior
  • Required — - description: Task description text
  • Optional — - due: Due date (ISO timestamp)
  • priority — Priority level ("H", "M", or "L")
  • mark_task_done — Mark a task as completed
  • Executes — task project:work next
  • TODO — Call my sister (high priority)
  • Tools — The Tools tool exposed by this server

Installing the taskwarrior mcp server

The server is distributed via npm as mcp-server-taskwarrior, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Where it fits

Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Taskwarrior sits in that group, and the shape of its toolset — get_next_tasks, project, tags among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • With 11 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Taskwarrior.
  • Maintained by awwaiid.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the taskwarrior mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
get_next_tasksGet a list of all pending tasks
projectFilter by project name
tagsFilter by one or more tags
add_taskAdd a new task to TaskWarrior
Required- description: Task description text
Optional- due: Due date (ISO timestamp)
priorityPriority level ("H", "M", or "L")
mark_task_doneMark a task as completed
Executestask project:work next
TODOCall my sister (high priority)
ToolsThe Tools tool exposed by this server.

How to install the Taskwarrior MCP server

{
  "mcpServers": {
    "taskwarrior": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-taskwarrior"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Taskwarrior to get next tasks.
  • Use Taskwarrior to project.
  • Use Taskwarrior to tags.

Frequently asked questions

It connects Taskwarrior to MCP-compatible AI assistants such as Claude and Cursor, exposing 11 tools (get_next_tasks, project, tags, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Taskwarrior directly.