# awwaiid/mcp-server-taskwarrior [Health: Active]

**Category:** 🛠️ Other Tools and Integrations  
**Repository:** https://github.com/awwaiid/mcp-server-taskwarrior  
**GitHub Stars:** 51  
**npm Downloads (last month):** 211  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/awwaiid-mcp-server-taskwarrior

## Description
An MCP server for basic local taskwarrior usage (add, update, remove tasks)

## Tools
Capabilities this server exposes over MCP:

- **project** — Filter by project name
- **tags** — Filter by one or more tags
- **description** — Task description text
- **due** — Due date (ISO timestamp)
- **priority** — Priority level ("H", "M", or "L")
- **identifier** — Task ID or UUID

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What awwaiid/mcp-server-taskwarrior MCP server does

The awwaiid/mcp-server-taskwarrior MCP server connects an MCP client to a local TaskWarrior installation. It supports a focused set of task operations: viewing pending work, creating tasks, and completing tasks. This makes it suitable for assistants that need to read or update a developer’s local task list without introducing a separate hosted task system.

The server exposes three tools:

- `get_next_tasks` returns pending tasks and can filter them by project or by one or more tags.
- `add_task` creates a task. A description is required; due date, priority, project, and tags are optional.
- `mark_task_done` completes a task using an ID or UUID as the identifier.

## How it works

The awwaiid/mcp-server-taskwarrior MCP server is implemented in Node.js and executes the local `task` command for TaskWarrior operations. MCP-compatible clients call the exposed tools, while TaskWarrior remains responsible for storing and managing the task data on the local system.

Task creation accepts an ISO timestamp for `due`. Priority values are limited to `H`, `M`, or `L`. Project names and tags are expected to use lowercase values; project names may contain dots. Pending-task queries can be narrowed to a project or to multiple tags.

The repository’s example client configuration uses `npx` to start the server. The README also shows operations corresponding to TaskWarrior commands such as listing work in a project, adding a high-priority task, and completing a task.

## Setup and configuration

Install and configure TaskWarrior first, ensuring the `task` binary is available on the machine where the MCP server runs. The awwaiid/mcp-server-taskwarrior MCP server does not replace the TaskWarrior installation or configuration.

For Claude Desktop, add a server entry that runs `npx -y mcp-server-taskwarrior`. The `-y` option accepts the package installation prompt automatically. No environment variables or API credentials are specified by the project material.

## Tools and capabilities

Use `get_next_tasks` to retrieve all pending tasks or limit results with `project` and `tags` filters. Use `add_task` when an assistant needs to create a task with a required description and optional due date, priority, project, or tags. Use `mark_task_done` to complete a task by supplying its identifier.

## Limitations and notes

The awwaiid/mcp-server-taskwarrior MCP server currently relies on TaskWarrior’s numeric task ID in some operations. The README warns that IDs can change when tasks are added or removed, making them unstable. UUID support is mentioned as a future direction, although the completion tool accepts either a task ID or UUID.

This is a local integration: TaskWarrior must be installed and configured, and the server runs the local executable. The provided material documents Claude Desktop usage but does not establish compatibility with other MCP clients.

_Full upstream README: https://allmcps.com/mcp/awwaiid-mcp-server-taskwarrior/readme_