Manage local TaskWarrior tasks through MCP by listing, filtering, adding, and completing tasks.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by MCP Server Taskwarrior.
projectFilter by project name
tagsFilter by one or more tags
descriptionTask description text
dueDue date (ISO timestamp)
priorityPriority level ("H", "M", or "L")
identifierTask ID or UUID
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.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.
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.
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.
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.
Factual signals from GitHub, npm, and our automated checks — not a rating.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/awwaiid-mcp-server-taskwarrior)<a href="https://allmcps.com/mcp/awwaiid-mcp-server-taskwarrior"><img src="https://allmcps.com/api/badge/awwaiid-mcp-server-taskwarrior?style=directory" alt="MCP Server Taskwarrior on AllMCPs" /></a>