Todoist MCP Server
Related Servers
Alternatives to Todoist MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA comprehensive MCP server that provides full integration between Claude and Todoist, enabling task, project, section, and label management through 24 different tools with the complete Todoist API.3017 npm6MIT
- FlicenseNot gradedqualityFmaintenanceMCP server that connects Claude to Todoist, enabling full CRUD operations on tasks, projects, sections, comments, and labels.-
- AlicenseAqualityCmaintenanceAn MCP server that integrates Claude with Todoist, enabling natural language task management including creating, updating, completing, and deleting tasks.5304 npm393MIT
- AlicenseBqualityDmaintenanceAn MCP server that connects Claude with Todoist for complete task and project management through natural language.86199 npm247MIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables advanced task and project management in Todoist via Claude Desktop and other MCP-compatible clients.144 npm2MIT
- AlicenseNot gradedqualityDmaintenanceA custom MCP server that connects Claude to Todoist using a permanent API token, avoiding OAuth re-authentication issues across all Claude surfaces.144 npmMIT
TDQS
Scored across 15 tools
Each tool has a distinct purpose: task CRUD, comment operations, label management, and project listing. There is no overlap that would confuse an agent; even similar tools like update_task and batch_update_tasks are clearly differentiated by scope.
All tools use snake_case verb_noun patterns, which is consistent. However, there is a minor inconsistency: some tools include 'todoist' (e.g., create_todoist_label) while others do not (e.g., create_task). This is a small deviation from a pure pattern.
15 tools cover the main Todoist entities (tasks, comments, labels, projects) without being overwhelming. The count is well-scoped for the server's purpose.
The tool set is missing several key operations: no create/delete/rename projects, no get single task by ID, no delete or update comments. These gaps would force agents to work around missing functionality, causing potential failures.