MCP server for Taskwarrior 3.x, TaskChampion, and Timewarrior task management.
If you already use TaskChampion MCP, the taskchampion mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Taskwarrior 3.x, TaskChampion, and Timewarrior task management.
TaskChampion MCP is a Model Context Protocol server that lets LLMs read, create, modify, and manage your Taskwarrior tasks and Timewarrior time entries. It wraps the task and timew CLI tools and exposes them as structured MCP tools that any compatible AI assistant can call.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
role — what the LLM can do (CONTRIBUTOR / GENERATOR / MANAGER)Code — tagged envelopes** — every tool response includes a stable code field for machine-safe branchingDry — run mode** — every destructive operation supports dry_run preview without mutationLLM — assisted contributions must be attributed (see docs/llm_context/AGENTS.md)Platform — TransportCursor — stdioWindsurf — stdioRole — Can ReadCONTRIBUTOR — ✅GENERATOR — ✅MANAGER — ✅Schema — DescriptionInstallation goes through your MCP client rather than a global install: point it at taskchampion-mcp on PyPI and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. TaskChampion MCP's toolset — role, Code, Dry and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GabiUp2; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| role | what the LLM can do (CONTRIBUTOR / GENERATOR / MANAGER) |
| Code | tagged envelopes** — every tool response includes a stable code field for machine-safe branching |
| Dry | run mode** — every destructive operation supports dry_run preview without mutation |
| LLM | assisted contributions must be attributed (see [docs/llm_context/AGENTS.md](docs/llm_context/AGENTS.md)) |
| Platform | Transport |
| Cursor | stdio |
| Windsurf | stdio |
| Role | Can Read |
| CONTRIBUTOR | ✅ |
| GENERATOR | ✅ |
| MANAGER | ✅ |
| Schema | Description |
| minimal | Built-in fields only (priority, project, tags) |
| gtd | Getting Things Done (contexts, energy, next-actions) |
{
"mcpServers": {
"taskchampion": {
"command": "uvx",
"args": ["taskchampion-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.