ticktick-mcp-enhanced
Related Servers
Alternatives to ticktick-mcp-enhanced
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server that enables AI agents to manage Dida365/TickTick tasks, projects, tags, and habits through natural language, with full CRUD, search, and advanced V2 capabilities.2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating TickTick task management with AI applications, enabling task and project operations via natural language.5 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server for TickTick task management. Enables AI assistants to create, update, list, search, and complete tasks via natural language.50 npm29MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to your TickTick tasks, enabling task management through natural language.81MIT
- AlicenseCqualityDmaintenanceAgent-friendly CLI and MCP server for TickTick and Dida365 task management APIs, enabling project and task management with stable JSON output and OAuth authentication.171MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with TickTick task management system through MCP, allowing users to view, create, update, complete, and delete tasks and projects via natural language.-
TDQS
Scored across 21 tools
Most tools target a distinct resource and action (create/update/delete/query per entity), and descriptions are detailed enough to separate them. Minor overlap exists between get_project_info and query_tasks (both return tasks within a project) and between create_tasks' items parameter and the dedicated create_subtasks tool.
The overwhelming majority follow a clear verb_noun pattern (create_tasks, update_projects, get_all_habits, checkin_habits), making the convention predictable. Minor deviations: ticktick_status and login break the pattern by being noun-style and bare-verb respectively.
At 21 tools, this sits in the heavy range, though each tool maps to a genuine operation across three resource types (projects, tasks, habits) plus auth. The count is defensible for a full-featured task manager, but an agent faces a large surface to navigate.
Projects and tasks have thorough lifecycle coverage (create/read/update/delete/complete/move/query), and habits have get/create/update/checkin coverage. However, there is no delete_habits tool, leaving habits without a deletion path, and subtasks only support creation with no dedicated update/delete operations.