Dida365 (TickTick) MCP Server
Related Servers
Alternatives to Dida365 (TickTick) MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage tasks and projects in TickTick through the TickTick Open API, supporting CRUD operations on tasks and projects.11 npm4MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage TickTick tasks and projects through OAuth2 authentication, supporting task creation, updates, completion, project management, and smart daily scheduling based on priorities and due dates.55MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage TickTick tasks including listing, creating, updating, completing, and deleting tasks, as well as searching and filtering.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to directly manage Dida365 (TickTick) tasks, including creating, editing, completing, and setting priorities, deadlines, subtasks, reminders, and recurring tasks via natural language.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage TickTick tasks through natural language, including creating, updating, completing, and deleting tasks, as well as managing projects.14MIT
- AlicenseBqualityAmaintenanceEnables AI assistants to read and write TickTick/Dida365 tasks, projects, tags, habits, and calendars through the service's private web API using browser session-cookie authentication. It exposes 34 tools covering task creation, completion, search, batch operations, trash restore, and full-account delta sync.3879 npmMIT
TDQS
Scored across 5 tools
The tool names are highly generic and vague, making it impossible to distinguish their purposes. Tools like 'api-client', 'data-processor', 'file-handler', and 'my-tool' could easily overlap in functionality, and 'example_tool' adds confusion without clear differentiation. This lack of specificity will likely cause agents to misselect tools due to ambiguous boundaries.
The naming conventions are inconsistent, mixing kebab-case (e.g., 'api-client'), snake_case (e.g., 'example_tool'), and camelCase (e.g., 'MyTool' in 'my-tool'). There is no predictable pattern in verb usage or structure, leading to a chaotic and unreadable set that lacks coherence.
With 5 tools, the count is reasonable for a server, but it feels borderline due to the vague and overlapping purposes. For a TickTick integration, this number might be thin if it aims to cover core task management features, but it's not extreme enough to score lower.
Given the server's name suggests a TickTick (Dida365) integration, the tool set is severely incomplete. There are no tools for core task management operations like creating, listing, updating, or deleting tasks, notes, or reminders. The generic tool names provide no coverage for the domain, leaving obvious gaps that will cause agent failures.