TickTick/Dida365 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIDA365_TOKEN | Yes | Your TickTick/Dida365 API token (should be prefixed with 'Bearer') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_taskB | Create a new task in Dida365 with specified details including title, project ID, content, due date and priority. The task will be created under the specified project. Requires at least title and projectId. Returns the created task details. |
| get_task_by_projectId_and_taskIdB | Retrieve a specific task's details by providing both the project ID and task ID. Returns complete task information including title, content, status, due date, priority, and subtasks if any. |
| get_tasks_by_projectIdB | Get all tasks belonging to a specific project by project ID. Returns a list of tasks with their basic information. Useful for viewing all tasks in a project. |
| update_taskB | Modify an existing task's properties. Can update title, content, due date, priority or status. At least taskId is required. Returns the updated task details. |
| delete_taskA | Permanently delete a task from a project. Requires both task ID and project ID for confirmation. Returns success message upon deletion. |
| complete_taskB | Mark a task as completed. Requires both task ID and project ID. Updates the task's status to completed and sets completion timestamp. |
| get_projectsA | Retrieve a list of all projects in the Dida365 account. Returns project details including ID, name, color, view mode and sort order. No parameters required. |
| get_project_by_projectIdC | Get detailed information about a specific project by its ID. Returns project metadata including name, color, view mode, kind and sort order. |
| create_projectB | Create a new project in Dida365. Requires at least a project name. Can specify color, view mode, kind and sort order. Returns the created project details. |
| update_project_by_projectIDC | Update an existing project's properties. Requires project ID. Can modify name, color, view mode, kind and sort order. Returns updated project details. |
| delete_project_by_projectIDA | Permanently delete a project by its ID. This will also delete all tasks within the project. Returns success message upon deletion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| 滴答清单任务 | 获取所有任务的概览 |
| 滴答清单项目 | 获取所有项目的概览 |
TDQS
Scored across 11 tools
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.
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.
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.
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.