MCP server for TickTick integration
MCP server for TickTick integration. The ticktick mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
A Model Context Protocol (MCP) server that provides integration with TickTick task management service.
Everything the assistant can do here goes through one of these:
get_tasks — Get all tasks or tasks from a specific project (with enhanced display)get_overdue_tasks — Get overdue tasks with timezone compensation (configurable offset, defaults to UTC+8 - adjust for your timezone)get_todays_tasks — Get tasks due today with D+1 timezone adjustmentget_projects — Get all projects from TickTickcreate_task — Create a new task with priority, tags, due datesupdate_task — Update an existing taskdelete_task — Delete a taskcomplete_task — Mark a task as completedget_task — Get a specific task by IDDevelopment — The Development tool exposed by this serverProduction — The Production tool exposed by this serverYou will need 6 environment variables: TICKTICK_ACCESS_TOKEN, TICKTICK_REFRESH_TOKEN, TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME, TICKTICK_PASSWORD. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. TickTick's toolset — get_tasks, get_overdue_tasks, get_todays_tasks and 8 more — is a fair guide to whether it matches your workflow. It is maintained by rafliruslan; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_tasks | Get all tasks or tasks from a specific project (with enhanced display) |
| get_overdue_tasks | Get overdue tasks with timezone compensation (configurable offset, defaults to UTC+8 - adjust for your timezone) |
| get_todays_tasks | Get tasks due today with D+1 timezone adjustment |
| get_projects | Get all projects from TickTick |
| create_task | Create a new task with priority, tags, due dates |
| update_task | Update an existing task |
| delete_task | Delete a task |
| complete_task | Mark a task as completed |
| get_task | Get a specific task by ID |
| Development | The Development tool exposed by this server. |
| Production | The Production tool exposed by this server. |
{
"mcpServers": {
"ticktick": {
"command": "node",
"args": ["/path/to/ticktick-mcp-server/dist/index.js"],
"env": {
"TICKTICK_ACCESS_TOKEN": "your_oauth_token",
"TICKTICK_REFRESH_TOKEN": "your_refresh_token",
"TICKTICK_CLIENT_ID": "your_client_id",
"TICKTICK_CLIENT_SECRET": "your_client_secret"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| TICKTICK_ACCESS_TOKEN | Credential the server authenticates with. | Yes |
| TICKTICK_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| TICKTICK_CLIENT_ID | Configuration value read at startup. | Optional |
| TICKTICK_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| TICKTICK_USERNAME | Configuration value read at startup. | Optional |
| TICKTICK_PASSWORD | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.