A
licenseA
qualityD
maintenanceA Model Context Protocol server that integrates with TickTick task management service, allowing AI assistants to list, create, update, and complete tasks with proper timezone handling.
9
5
MIT
TickTick/Dida365 MCP Server
by ZH1754629545
Related Servers
Alternatives to TickTick/Dida365 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI assistants to your TickTick tasks, enabling task management through natural language.81MIT
- 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
- AlicenseCqualityDmaintenanceA comprehensive Model Context Protocol server providing complete TickTick task management API integration (112 operations) for Claude Code users, enabling seamless task creation, project management, habit tracking, and productivity features.10011MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to manage Google Tasks, including creating, updating, deleting, and searching tasks and task lists via OAuth2 authentication.22 npm1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables management of TickTick tasks and projects through the Model Context Protocol, supporting deployment on Vercel with SSE capabilities. Users can list, create, update, and complete tasks directly within AI clients like Claude.1-
TDQS
A3.7/5.0
Scored across 11 tools
Disambiguation5/5
Each tool has a distinct purpose with clear boundaries: 'complete_task' marks completion, 'create_project' and 'create_task' handle creation, 'delete_project_by_projectID' and 'delete_task' handle deletion, 'get_project_by_projectId' and 'get_task_by_projectId_and_taskId' retrieve specific items, 'get_projects' and 'get_tasks_by_projectId' list items, and 'update_project_by_projectID' and 'update_task' handle updates. No overlap or ambiguity exists between tools.
Naming Consistency4/5
Most tools follow a consistent verb_noun pattern (e.g., 'create_project', 'delete_task', 'update_project_by_projectID'), but there are minor deviations: 'get_project_by_projectId' uses 'Id' inconsistently (camelCase) while others use 'ID', and 'get_task_by_projectId_and_taskId' has a longer, less standard format. Overall, naming is highly readable and predictable.
Tool Count5/5
With 11 tools, the count is well-scoped for a task management server, covering core operations like CRUD for projects and tasks, plus specific actions like completing tasks. Each tool serves a clear purpose without redundancy, fitting typical expectations for such a domain.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for both projects and tasks in Dida365: creation, retrieval (specific and list), updating, and deletion are all supported, along with task completion. No obvious gaps exist; agents can perform all essential operations without dead ends.
Maintenance
ActivityInactive
ResponsivenessUnresponsive