Ticktick MCP

Ticktick MCP runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/partymola/ticktick-mcp:v0.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm -e TICKTICK_CLIENT_ID -e TICKTICK_CLIENT_SECRET -e TICKTICK_USERNAME -e TICKTICK_PASSWORD ghcr.io/partymola/ticktick-mcp:v0.5.0. It reads these environment variables: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET (secret), TICKTICK_USERNAME and TICKTICK_PASSWORD (secret); set them in the client's configuration for this server. Required arguments: --user and -v.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "ticktick-mcp": {
      "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.5.0"
      ],
      "env": {
        "TICKTICK_CLIENT_ID": "<value>",
        "TICKTICK_CLIENT_SECRET": "<secret>",
        "TICKTICK_USERNAME": "<value>",
        "TICKTICK_PASSWORD": "<secret>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect