TickTick MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_tasksB | Get all tasks or tasks from a specific project |
| get_overdue_tasksA | Get all overdue tasks (incomplete tasks past their due date) |
| get_todays_tasksB | Get tasks that are specifically due today |
| get_projectsB | Get all projects from TickTick |
| create_taskC | Create a new task in TickTick |
| update_taskC | Update an existing task |
| delete_taskC | Delete a task |
| complete_taskC | Mark a task as completed |
| get_taskC | Get a specific task by ID |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, get_tasks retrieves all tasks or project-specific tasks, while get_overdue_tasks and get_todays_tasks filter by due date, and get_task fetches a single task by ID. The action verbs (complete, create, delete, get, update) are consistently paired with specific nouns (task, projects) to avoid overlap.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_task, get_projects, and update_task. There are no deviations in naming conventions, making the set predictable and easy to understand at a glance.
With 9 tools, the server is well-scoped for task management in TickTick. Each tool earns its place by covering essential operations like CRUD for tasks, project retrieval, and filtered task views (e.g., overdue, today), without being overly sparse or bloated.
The tool surface provides complete CRUD/lifecycle coverage for tasks (create, get, update, delete, complete) and includes project management (get_projects) and filtered views (overdue, today). There are no obvious gaps, as all core operations for task and project handling are covered without dead ends.