Ticktick MCP

Name: Ticktick MCP
Author: partymola

by partymolaversion 0.7.0i★ –iRuns on your computer

Registry nameio.github.partymola/ticktick-mcp

Install

Overview

Description from the maker (original English)

MCP server for TickTick task management: field-preserving updates and completion tracking.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Docs, sheets & office work
You need to fill in: TICKTICK_CLIENT_SECRET, TICKTICK_PASSWORD

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_USERNAME, TICKTICK_PASSWORD

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ticktick": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TICKTICK_CLIENT_ID",
        "-e",
        "TICKTICK_CLIENT_SECRET",
        "-e",
        "TICKTICK_USERNAME",
        "-e",
        "TICKTICK_PASSWORD",
        "ghcr.io/partymola/ticktick-mcp:v0.7.0"
      ],
      "env": {
        "TICKTICK_CLIENT_ID": "your-value",
        "TICKTICK_CLIENT_SECRET": "your-value",
        "TICKTICK_USERNAME": "your-value",
        "TICKTICK_PASSWORD": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ticktick --env TICKTICK_CLIENT_ID=your-value --env TICKTICK_CLIENT_SECRET=your-value --env TICKTICK_USERNAME=your-value --env TICKTICK_PASSWORD=your-value -- docker run -i --rm -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET -e TICKTICK_USERNAME -e TICKTICK_PASSWORD ghcr.io/partymola/ticktick-mcp:v0.7.0

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ticktick": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TICKTICK_CLIENT_ID",
        "-e",
        "TICKTICK_CLIENT_SECRET",
        "-e",
        "TICKTICK_USERNAME",
        "-e",
        "TICKTICK_PASSWORD",
        "ghcr.io/partymola/ticktick-mcp:v0.7.0"
      ],
      "env": {
        "TICKTICK_CLIENT_ID": "your-value",
        "TICKTICK_CLIENT_SECRET": "your-value",
        "TICKTICK_USERNAME": "your-value",
        "TICKTICK_PASSWORD": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ticktick": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "TICKTICK_CLIENT_ID",
        "-e",
        "TICKTICK_CLIENT_SECRET",
        "-e",
        "TICKTICK_USERNAME",
        "-e",
        "TICKTICK_PASSWORD",
        "ghcr.io/partymola/ticktick-mcp:v0.7.0"
      ],
      "env": {
        "TICKTICK_CLIENT_ID": "your-value",
        "TICKTICK_CLIENT_SECRET": "your-value",
        "TICKTICK_USERNAME": "your-value",
        "TICKTICK_PASSWORD": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

TICKTICK_CLIENT_ID env
TickTick OAuth client ID. Needed only if you are not mounting a .env file.
TICKTICK_CLIENT_SECRET secret env
TickTick OAuth client secret. Needed only if you are not mounting a .env file.
TICKTICK_USERNAME env
TickTick account username. Needed only if you are not mounting a .env file.
TICKTICK_PASSWORD secret env
TickTick account password. Needed only if you are not mounting a .env file.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account partymola, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Docs, sheets & office worki

More stars than 0% of the other 3544 servers in this category
Published to the registry more recently than 92% of the other 3544 servers in this category
Basic checks equal to or better than 100% of the other 3544 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Ticktick MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: TICKTICK_CLIENT_SECRET, TICKTICK_PASSWORD

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.7.0) reached the registry 2 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Agent-Native Calendar

by BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

Runs in the cloud★ 7,620MITUpdated 2 months ago

Install

Excel MCP Server

by haris-musa

Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.

Runs on your computer★ 4,276MITUpdated 7 days ago

Install

MCP Server for Excel

by sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

Runs on your computer★ 847MITUpdated 4 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ticktick-mcp

MCP server for TickTick task management. Create, update, complete, move, and filter tasks through TickTick's Open and v2 APIs, with field-preserving updates, day-of-week date validation, read-after-write verification, and idempotent completion tracking.

Designed for Claude Code and other MCP clients.

Unofficial. Not affiliated with TickTick Ltd. Built on ticktick-py (MIT).

Features

Full task lifecycle - create, update, complete, move, subtask, and delete
Field-preserving updates - ticktick_update_task re-fetches the task and overlays only the fields you set, sending its other editable fields back with them
Day-of-week validation - any call that sets a date must confirm the weekday, catching off-by-one date mistakes before they reach the server
Read-after-write verification - create/update compare the server's response with what was sent and surface _verification_warnings when it doesn't match
Compact listing - list tools return a trimmed view by default so large projects stay under the MCP result-size cap (see below)
Fresh reads - read tools re-sync server state on demand, so edits made from the TickTick app on other devices show up without a restart
Completion tracking - mark completed tasks as processed so an agent reviews each one exactly once, and completions made through this server record themselves

Requirements

Python 3.13+ (tested on 3.13, 3.14 and 3.15, on Linux, macOS and Windows, in CI)
uv (recommended - see the install note below)
A TickTick account
A registered TickTick app for OAuth credentials (free - developer.ticktick.com)

Install

git clone https://github.com/partymola/ticktick-mcp

cd ticktick-mcp uv sync

This creates a .venv and installs from uv.lock, giving you the console script at .venv/bin/ticktick-mcp, or .venv\Scripts\ticktick-mcp on Windows. Every command below names it the POSIX way.

pip install . works too. The fork of ticktick-py this server needs is pinned as a direct git reference inside dependencies, which pip and uv both honour; uv sync is recommended because it installs the exact versions in uv.lock rather than re-resolving them.

Credentials

TickTick sign-in needs two things: an OAuth app (client ID + secret) and your own account login.

Register an app at developer.ticktick.com. Set the Redirect URI to http://localhost:8080/redirect. Note the Client ID and Client Secret.
Copy the template into the directory the server reads, and fill it in:

   mkdir -p ~/.config/ticktick-mcp && cp .env.example ~/.config/ticktick-mcp/.env

   TICKTICK_CLIENT_ID=your_client_id

TICKTICK_CLIENT_SECRET=your_client_secret TICKTICK_REDIRECT_URI=http://localhost:8080/redirect TICKTICK_USERNAME=your_ticktick_email TICKTICK_PASSWORD=your_ticktick_password

This file holds your account password in plain text, and the server does not create it, so tighten it yourself. On POSIX:

   chmod 700 ~/.config/ticktick-mcp

chmod 600 ~/.config/ticktick-mcp/.env

Those are POSIX mode bits, and on Windows they do nothing: access there follows the ACLs the file inherits from its parent directory. No Windows equivalent of the two commands is documented here.

The two token files beside it are created owner-only, and a config directory the server creates is too - but one it finds already there is left as it is. Those are POSIX modes as well, set on Windows too, where they do not narrow who may read what.

Authorise once, at a terminal, before registering the server:

.venv/bin/ticktick-mcp auth

It opens a browser and asks you to paste back the URL you land on, then exits. The token is cached next to your .env as .token-oauth, and every later start reuses it. TickTick issues no refresh token, so this recurs when the token expires - run the same command again.

Do not let that step happen inside the MCP server. The prompt reads from standard input, which for a stdio server is the JSON-RPC channel, so an unauthorised first tool call opens a browser on the host and blocks. In a container it cannot be completed at all - run auth on the host and mount the config directory in.

The username/password half needs no separate step: the server logs in lazily on the first tool call and caches that session token as .token-v2, so it does not re-submit your credentials on every start.

The server looks for .env in this order: the --dotenv-dir argument, then the TICKTICK_MCP_DOTENV_DIR environment variable, then ~/.config/ticktick-mcp/. If no .env is found it falls back to the TICKTICK_* environment variables directly, which is convenient for container/CI use.

Privacy and the unofficial API

Your TickTick credentials live only in your local .env (or the environment) and are sent only to TickTick's own servers - never to the developer or any third party. The server reads and writes only your own account.

This server relies on TickTick's unofficial v2 API (via ticktick-py) rather than only the official Open API. That is a deliberate choice: the official API has no list-completed-tasks endpoint, no tags, and no cross-project task listing - all of which this server relies on. Reads, completed lists, delete, move and subtask go through v2, as does removing a reminder. Create, update and complete use the Open API. See docs/why-not-the-official-api.md for the full rationale, the risk trade-off, and the triggers that would make us reconsider.

Register with Claude Code

claude mcp add -s user ticktick -- /path/to/ticktick-mcp/.venv/bin/ticktick-mcp --dotenv-dir /path/to/config

--dotenv-dir is optional if your .env lives in ~/.config/ticktick-mcp/ or you supply the TICKTICK_* variables through the environment.

Then ask Claude things like:

"What's on my TickTick list for this week?"
"Add a task to call the dentist on Friday at 9am."
"Mark the grocery task as done."
"Move the budget task to the Finance project."

Docker

Images are published to ghcr.io/partymola/ticktick-mcp. Tags carry a v prefix (:vX.Y.Z), and :latest follows the most recent release.

Authorise on a machine with a browser first, then mount that directory in. This is the only route, and it holds even with docker run -it: the underlying library opens the browser itself and never prints the URL, so there is nothing to copy out of a container that has no browser. It then waits for that URL on standard input, which for a stdio server is the JSON-RPC channel - so a container started against a directory with no cached token does not fail cleanly either, it consumes your client's requests waiting for input that never arrives.

Authorising needs a source install (Install) and the credentials from Credentials - there is no published package to run it from. Do not `pip install ticktick-mcp`: that name on PyPI belongs to an unrelated project with a near-identical description.

.venv/bin/ticktick-mcp auth       # once, on the host, in a terminal

claude mcp add -s user ticktick -- \ docker run --rm -i --user $(id -u):$(id -g) \ -v ~/.config/ticktick-mcp:/data \ ghcr.io/partymola/ticktick-mcp:latest

-i is required - the server speaks JSON-RPC over stdin and stdout.

--user is there because the container runs as root by default, and anything it writes into the mounted directory becomes root-owned - after which the host-side ticktick-mcp can no longer update its session-token cache and falls back to a throttled signon on every start. You will run it on the host again: the OAuth token has no refresh, so auth recurs at expiry.

Mount a directory that is already authorised, never an empty volume. /data holds the .env, the cached OAuth token, the v2 session token and the completion-tracking database. A fresh volume has none of them, and the password-signon fallback is throttled into a 15-30 minute lockout.

If you would rather not keep a .env on disk at all, pass the credentials as environment variables instead. The mount is still needed - it holds the token cache, not just the .env:

docker run --rm -i --user $(id -u):$(id -g) \

-v ~/.config/ticktick-mcp:/data \ -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET \ -e TICKTICK_USERNAME -e TICKTICK_PASSWORD \ ghcr.io/partymola/ticktick-mcp:latest

Naming each variable without a value passes it through from your shell, so no secret appears in the command or in shell history. These override a mounted .env: the file is loaded without override, so anything already in the environment wins. Authorising still needs those variables exported on the host, since auth has no .env to read either.

CLI

ticktick-mcp                       Start the MCP server (stdio transport)

ticktick-mcp --dotenv-dir PATH Directory holding the .env file ticktick-mcp --version Print the installed package version

auth is the only other subcommand, and it exists so the browser step happens at a terminal rather than inside the server. All task operations happen through the MCP tools below.

MCP tools

Tool	Description
`ticktick_create_task`	Create a task, preserving date/reminder/priority/timezone fields; attaches `_verification_warnings` for anything worth knowing about what landed
`ticktick_update_task`	Update a task by overlaying only the fields you set onto the current server object
`ticktick_complete_task`	Mark a task complete and re-verify; distinguishes a recurring task rolling forward from a normal completion, and records the completion as processed
`ticktick_delete_tasks`	Delete one or more tasks by ID
`ticktick_move_task`	Move a task into a different project
`ticktick_make_subtask`	Nest one task as a subtask of another in the same project
`ticktick_get_tasks_from_project`	List every open task in a project (compact or full)
`ticktick_filter_tasks`	Find tasks by any mix of project, priority, tag, status, and due/completion-date window
`ticktick_get_by_id`	Look up any task, project, or tag by its full ID
`ticktick_get_all`	Dump all projects or all tags from local state
`ticktick_sync`	Force an immediate refresh of local state from the server
`ticktick_get_unprocessed_completions`	List recently completed tasks in a project not yet marked processed; in practice, the ones completed outside this server
`ticktick_mark_completion_processed`	Record that a completed task has been reviewed, excluding it from future checks
`ticktick_convert_datetime_to_ticktick_format`	Convert an ISO 8601 datetime + IANA timezone to TickTick's wire format

Projects: name or ID

Every tool that takes a project ID also takes the project's name - ticktick_create_task, ticktick_get_tasks_from_project, ticktick_update_task, ticktick_move_task, ticktick_delete_tasks, ticktick_filter_tasks, and both completion-tracking tools:

ticktick_create_task(title

Only the beginning is shown; read the rest in the repo

Ticktick MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Docs, sheets & office worki

Common questions

Alternatives

Agent-Native Calendar

Excel MCP Server

MCP Server for Excel

README from the maker

ticktick-mcp

Features

Requirements

Install

Credentials

Privacy and the unofficial API

Register with Claude Code

Docker

CLI

MCP tools

Projects: name or ID