MCP.so
Sign In
T

Ticktick Api MCP (typescript)

@polza-ai

Basic information

Category

Developer Tools

Transports

stdio

Author

polza-ai

Submitted by

dddoker

About Ticktick Api MCP

No overview available yet

Ticktick Api MCP config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ticktick": {
      "command": "node",
      "args": [
        "/absolute/path/to/ticktick-mcp-ts/dist/index.js"
      ],
      "env": {
        "TICKTICK_ACCESS_TOKEN": "your_access_token_here",
        "TICKTICK_BASE_URL": "https://api.ticktick.com/open/v1"
      }
    }
  }
}

Ticktick Api MCP tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Ticktick Api Mcp (typescript)?

It is a Model Context Protocol (MCP) server written in TypeScript that integrates with the TickTick task management API. It allows AI clients like Claude to manage projects and tasks in TickTick through a standardized interface.

How to use Ticktick Api Mcp (typescript)?

Install with npm install and build with npm run build. Configure environment variables in a .env file with your TickTick Client ID, Client Secret, and Access Token. Run npm run get-token to obtain an access token via OAuth2. Then add the server to your MCP client’s configuration (e.g., Claude Desktop) pointing to the built dist/index.js file. Tools are invoked automatically by the client based on user requests.

Key features of Ticktick Api Mcp (typescript)

  • OAuth2 authentication using an access token
  • Full CRUD for projects and tasks
  • Special tools to fetch today’s and overdue tasks
  • Separate script (npm run get-token) to obtain credentials
  • Dynamic resources for configuration, projects, tasks, and stats
  • Supports both TickTick and its Chinese version Dida365

Use cases of Ticktick Api Mcp (typescript)

  • List all TickTick projects and their tasks via Claude
  • Create, update, or delete tasks and projects on demand
  • Get a summary of today’s deadlines or overdue items
  • Automate task planning: “Create a project with a set of tasks for my event”
  • Integrate TickTick task management into an AI‑powered workflow

Frequently asked questions

1

What is the difference between TickTick and Dida365?

Dida365 is the Chinese version of TickTick. The server supports both by changing the base URL and auth endpoints in the `.env` file (e.g., `TICKTICK_BASE_URL=https://api.dida365.com/open/v1`). The OAuth flow is identical.

2

What runtime and dependencies are required?

Node.js 18 or higher, npm or yarn, and a TickTick API application (Client ID and Client Secret) registered at the TickTick Developer Center.

3

Where are user credentials and data stored?

Credentials (Client ID, Client Secret, Access Token) are stored locally in the `.env` file. No user data is stored by the server; it only makes API calls to TickTick’s servers.

4

Can I use the server without setting up a `.env` file?

Yes, each tool accepts an optional `accessToken` parameter. If omitted, the server reads `TICKTICK_ACCESS_TOKEN` from the environment. All other configuration (base URLs) must be set in the environment or default values are used.

5

How does authentication work?

The server uses OAuth2. Run `npm run get-token` to start a local server on port 8080, open a browser for TickTick login, and automatically save the access and refresh tokens. The server handles token refresh automatically when needed.

Comments

More Developer Tools MCP servers