How Claude + TickTick Can Superpower Your Workflow

2026-03-24 · 4 min read

// what you can do

When Claude is connected to TickTick, your task management becomes conversational:

"What's on my list for today?" — Claude checks your TickTick and gives you a prioritized summary.
"Add 'review quarterly report' to my work project, due Friday." — Claude creates the task with the right project and deadline.
"Move the dentist appointment to next Tuesday." — Claude reschedules it without you opening the app.
"Create a project called 'Kitchen Remodel' with tasks for getting quotes, choosing materials, and scheduling contractors." — Claude builds the project structure.
"Mark 'send invoice' as done." — Claude completes it for you.
"What tasks are overdue?" — Claude finds them and helps you triage.

TickTick's MCP server exposes a rich set of tools — projects, tasks, tags, and more. Claude can read and write your entire task system.

// the catch

TickTick's MCP server uses OAuth with Dynamic Client Registration (DCR), the same pattern that causes headaches with Notion. MCP clients need to handle DCR registration, token exchange, and session management correctly — and most don't.

The result: you authorize TickTick, it looks like it works, and then every tool call returns 401 Unauthorized. This is a known issue affecting users in both Claude and Cursor.

Even when the initial connection works, DCR client registrations can expire. When that happens, the MCP client loses its ability to refresh tokens and the connection silently breaks.

// how Bindify fixes it

Bindify sits between Claude and TickTick. You authenticate once through Bindify's dashboard — either via OAuth or by pasting a TickTick API token — and Bindify maintains the connection on your behalf.

Claude gets a permanent URL. No DCR to manage. No token refresh to handle. No 401 errors. Your TickTick connection works the same way on day 1 as it does on day 100.

// setup guide

Step 1: Create a Bindify account

Step 2: Connect TickTick

Click "Add Connection" and select TickTick. You have two options:

OAuth: Click "Connect with OAuth" and authorize Bindify. One-time setup.
API Token: In TickTick, click your profile avatar (top-left) → Settings → API Token (Manage) → Copy. Paste it into Bindify.

Step 3: Add to Claude

Copy your secret URL from the dashboard, then add it to your Claude client:

Claude.ai (Web)

Click Settings (gear icon, bottom-left)
Click Connectors
Click Add custom connector
Name it "TickTick via Bindify"
Paste your secret URL

Claude Desktop

Go to Settings > Connectors > Add custom connector and paste your secret URL.

Or edit the config file:

{
  "mcpServers": {
    "ticktick": {
      "url": "https://api.bindify.dev/mcp/ticktick/{secret}"
    }
  }
}

Claude Code (CLI)

claude mcp add ticktick \
  --transport streamable-http \
  "https://api.bindify.dev/mcp/ticktick/{secret}"

Step 4: Done

Start a conversation and ask Claude to list your tasks. It will just work — permanently.

// you're not alone

TickTick MCP auth issues are widely reported:

r/ticktick: "TickTick MCP only returns 401 in both Claude and Cursor" — users getting 401 on every request after authorization

Connect TickTick Now

24-hour free trial. No credit card required.