A Model Context Protocol (MCP) server for TickTick integration
Connect Ticktick to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for TickTick integration. The ticktick mcp server is what makes that connection.
A Model Context Protocol (MCP) server for TickTick task management integration. This server allows AI assistants like Claude to interact with your TickTick account to manage tasks and projects.
The server ships on npm as ticktick-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Authentication — The Authentication tool exposed by this serverUser — The User tool exposed by this serverProjects — The Projects tool exposed by this serverTasks — The Tasks tool exposed by this serverConfiguration is passed through the environment: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_REDIRECT_URI, TICKTICK_REGION. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
You'll need TickTick API credentials: 1. Go to TickTick Developer Portal 2. Create a new application 3. Note your Client ID and Client Secret 4. Set the redirect URI to http://localhost:8080/callback (or your preferred callback URL)
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 — Authentication, User, Projects and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jordyvd; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Authentication | The Authentication tool exposed by this server. |
| User | The User tool exposed by this server. |
| Projects | The Projects tool exposed by this server. |
| Tasks | The Tasks tool exposed by this server. |
{
"mcpServers": {
"ticktick-1": {
"command": "npx",
"args": ["-y", "ticktick-mcp"],
"env": {
"TICKTICK_CLIENT_ID": "your-value",
"TICKTICK_CLIENT_SECRET": "your-value",
"TICKTICK_REDIRECT_URI": "your-value",
"TICKTICK_REGION": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
You'll need TickTick API credentials: 1. Go to TickTick Developer Portal 2. Create a new application 3. Note your Client ID and Client Secret 4. Set the redirect URI to http://localhost:8080/callback (or your preferred callback URL)
| Variable | Description | Required |
|---|---|---|
| TICKTICK_CLIENT_ID | Configuration value read at startup. | Optional |
| TICKTICK_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| TICKTICK_REDIRECT_URI | Filesystem location the server is allowed to use. | Optional |
| TICKTICK_REGION | 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.