ticktick-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKTICK_API_TOKEN | No | TickTick personal API token to use as a fallback when browser OAuth login is not possible. Takes precedence over the OAuth file. | |
| TICKTICK_TOKEN_FILE | No | Path to a file containing a TickTick personal API token, used as a fallback when browser OAuth login is not possible. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
TickTick task manager. Start with list_projects to get project IDs, then list_tasks or create_task. Destructive tools require confirm:true after the user agrees.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List TickTick projects, including the Inbox alias, with their IDs, names, colors and permissions. Use the returned projectId in task tools. |
| get_projectA | Get one TickTick project. With includeTasks true (default) it also returns the project columns and its open tasks; with false, count, tasks and columns are null. |
| create_projectB | Create a TickTick project and return its new ID. |
| update_projectB | Rename or change the color, view or kind of an existing TickTick project. |
| delete_projectA | Permanently delete a TickTick project. Requires confirm:true; ask the user first. Prefer closing tasks or moving them when unsure. |
| list_tasksA | List TickTick tasks, optionally limited to one project or "inbox". Status can be open, completed or all; results are capped at 200. |
| filter_tasksA | Find TickTick tasks by project, date range, priority, tags or status. Use this for agendas and due-date queries; results are capped at 200. |
| search_tasksA | Search TickTick tasks by keyword, with optional project, tag, status and due-date filters. Results are capped at 200. |
| get_taskA | Get one TickTick task by projectId and taskId, including its checklist and recurrence. |
| create_taskB | Create a TickTick task in a project. Dates accept YYYY-MM-DD or ISO 8601; priority accepts none/low/medium/high or 0/1/3/5. |
| update_taskA | Update fields on an existing TickTick task. Omitted fields stay unchanged. Use complete_task to mark it done or move_tasks to move it. |
| complete_taskA | Mark one TickTick task completed, or complete up to 50 tasks in one project by passing taskIds. For taskIds, omit projectId to use the inbox. |
| delete_taskA | Permanently delete a TickTick task. Requires confirm:true; ask the user first. |
| move_tasksC | Move up to 50 TickTick tasks from one project to another. |
| manage_tagsA | List TickTick tags, or create one. Use action "list" to see tags, or action "create" with a name. |
| manage_commentsA | List, add or delete comments on a TickTick task. Use action "list", "add" with content, or "delete" with commentId and confirm:true. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Several task-retrieval tools overlap: list_tasks, filter_tasks, and search_tasks all return tasks and could be confused depending on whether the agent needs a simple list, date/priority filtering, or keyword search. Descriptions provide guidance, but the boundaries are not crisp enough to prevent occasional misselection.
All tool names follow a consistent verb_noun pattern: list_projects, get_project, create_task, update_task, complete_task, move_tasks, manage_tags, manage_comments, etc. The conventions are predictable and readable throughout.
At 16 tools, the surface is slightly heavy but justified by distinct resource areas: projects, tasks, tags, comments, and bulk operations. Each tool has a plausible role, though the three task-query tools could potentially be consolidated.
Core lifecycle coverage is strong: full CRUD for projects and tasks, plus completion and bulk movement. Minor gaps remain around tag update/delete, comment editing, and checklist/subtask mutation, but these are workaroundable and not central to most workflows.