todoist-mcp-server and taskwarrior-mcp
These are competitors—both provide MCP server interfaces for task management systems, allowing users to integrate their preferred task tool (Todoist's cloud-based system versus TaskWarrior's local GTD approach) into AI workflows, but serve mutually exclusive use cases depending on which underlying task manager a user has adopted.
About todoist-mcp-server
stanislavlysenko0912/todoist-mcp-server
Full implementation of Todoist Rest API & support Todoist Sync API for MCP server
Implements an MCP server that exposes Todoist's full REST and Sync APIs as conversational tools for Claude and other AI assistants, enabling natural language task management without requiring IDs. Supports batch operations and name-based search across tasks, projects, sections, labels, and comments, with configurable deployment across Claude Desktop, Cursor, Codex, and Gemini CLI via stdio transport.
About taskwarrior-mcp
omniwaifu/taskwarrior-mcp
MCP Server for TaskWarrior / GTD Tools
Wraps the TaskWarrior CLI via subprocess calls to expose 22 tools including GTD-specific operations like `get_next_actions` (filtered by context/energy/time), `weekly_review`, and dependency management—plus batch operations and recurring task tracking with streak metrics. Returns enriched JSON responses with task arrays, metadata counts, and relationship graphs. Integrates as an MCP server for Claude Desktop and other MCP clients via Node.js runtime, with optional `TASK_BIN` and `TASKRC` environment variables for non-default TaskWarrior configurations.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work