Question 1

What are the prerequisites for running Ticktick Mcp?

Accepted Answer

You need Python >= 3.10, a TickTick account, and API credentials (Client ID, Client Secret, Redirect URI) obtained from the TickTick OpenAPI Developer portal.

Question 2

How do I set up authentication?

Accepted Answer

Create a `.env` file with your credentials. On first run, an OAuth2 flow opens a browser for authorization; you must paste the full redirect URL (which contains a `code=` parameter) back into the terminal. A `.token-oauth` file is then created to cache the token for ~6 months.

Question 3

Where should the .env file be placed?

Accepted Answer

By default, the server looks for a `.env` file at `~/.config/ticktick-mcp/.env`. You can specify a different directory using the `--dotenv-dir` command-line argument when running the server directly via Python.

Question 4

What credentials does it need?

Accepted Answer

It reads `TICKTICK_CLIENT_ID`, `TICKTICK_CLIENT_SECRET` from the environment. Store these in your client's env block or a secrets manager — never commit them to a repository — and grant the narrowest scope that still covers your use case.

Variable	Description	Required
TICKTICK_CLIENT_ID	Configuration value read at startup.	Optional
TICKTICK_CLIENT_SECRET	Credential the server authenticates with.	Yes

Ticktick MCP Server

What is the Ticktick MCP Server?

What it actually does

Configuration

More MCP options

Configuration

Example prompts to try

Frequently asked questions

Alternatives to the Ticktick MCP Server

Memory

Sequential Thinking

Redmine

Memory

Tibiawiki-mcp

Arxiv