ticktick-mcp
Related Servers
Alternatives to ticktick-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for TickTick API enabling task management, project organization, habit tracking, and more.32 npm73MIT
- FlicenseNot gradedqualityDmaintenanceRemote MCP server for managing TickTick tasks and projects, offering 22 tools for CRUD, search, and GTD workflows via any MCP client.1-
- AlicenseNot gradedqualityCmaintenanceA security-hardened MCP server for TickTick that enables managing your tasks directly through any MCP-compatible client.27 PyPI1MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for TickTick task management. Enables AI assistants to create, update, list, search, and complete tasks via natural language.25 npm30MIT
- 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
- AlicenseNot gradedqualityDmaintenanceMCP server for integrating TickTick task management with AI applications, enabling task and project operations via natural language.10 npmMIT
TDQS
Scored across 14 tools
Each tool targets a distinct action (create, update, delete, complete, move, nest, sync), and the listing tools are differentiated by scope: get_tasks_from_project is project-scoped while filter_tasks is a general multi-criteria query. The main confusion source is get_all(search="tasks"), which overlaps with the other list tools and is even documented as inert, plus get_by_id vs get_all which both retrieve records but at different granularity.
All tools share the ticktick_ prefix and snake_case with clear verb_noun structure (create_task, update_task, delete_tasks, move_task, complete_task). Minor deviations exist: 'make_subtask' uses make rather than create, and the get family has three inconsistent forms (get_by_id, get_all, get_tasks_from_project), but overall it is predictable and readable.
14 tools sits comfortably in the well-scoped 3-15 range for a task manager. Each tool earns its place: core CRUD, completion workflow, project movement, subtasking, a datetime utility, and sync all map to real operations rather than padding.
The task lifecycle is well covered (create, read/filter, update, delete, complete, move, subtask) plus a completion-processing queue and sync. Minor gaps remain around project/tag lifecycle management (only listing exists, no create/delete of projects or tags) and no bulk update, but agents can work around these via the inbox and existing tools.