ticktick-mcp

Provides an MCP (Model Context Protocol) server that integrates with TickTick (and optionally Dida365) via TickTick’s/Open API, exposing MCP tools to view, create, update, complete, and delete projects/tasks.

Evaluated Mar 30, 2026 (22d ago)

Repo ↗ Automation mcp ticktick task-management oauth2 python productivity integration

⚙ Agent Friendliness

/ 100

Can an agent use this?

🔒 Security

/ 100

Is it safe for agents?

⚡ Reliability

/ 100

Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality

Documentation

Error Messages

Auth Simplicity

Rate Limits

🔒 Security

TLS Enforcement

Auth Strength

Scope Granularity

Dep. Hygiene

Secret Handling

Uses OAuth2 with browser-based authorization and token refresh. README implies tokens are saved to a local .env file, which is convenient but can be risky if file permissions/logging are not handled correctly. No details are provided on TLS enforcement for the token/client calls, token storage protections, or least-privilege scopes.

⚡ Reliability

Uptime/SLA

Version Stability

Breaking Changes

Error Recovery

Best When

You want an AI-agent-friendly interface (MCP) to your personal task system and are comfortable running a local Python server with OAuth authentication.

Avoid When

You need strict enterprise-grade auditability, centralized secret management, or guaranteed idempotent operations for retries.

Use Cases

• Using Claude or other MCP clients to manage TickTick tasks and projects
• Listing tasks/projects and querying tasks by due date, priority, or search term
• Creating/updating tasks and projects via natural language through MCP tool calls
• Implementing a lightweight GTD workflow (Engaged/Next) using MCP toolsets

Not For

• High-stakes automated changes without human review (task deletion/update can be destructive)
• Use as a general TickTick API replacement where HTTP/REST access and fine-grained control are required
• Environments where storing tokens in a local .env file is unacceptable

Interface

REST API

GraphQL

gRPC

MCP Server

Yes

SDK

Webhooks

Authentication

Methods: OAuth2 authorization code flow (browser redirect to local callback)

OAuth: Yes Scopes: No

README indicates OAuth2 for TickTick/Dida365 and token refresh handled automatically. Scopes and their granularity are not described.

Pricing

Free tier: No

Requires CC: No

Pricing for the MCP server itself is not discussed; costs would primarily be your own infrastructure and any TickTick API access constraints.

Agent Metadata

Pagination

none

Idempotent

False

Retry Guidance

Not documented

Known Gotchas

⚠ Tool calls can delete tasks/projects; agents may need explicit confirmation or guardrails before destructive actions.
⚠ Authentication stores tokens in a local .env file; agent environments must handle secure filesystem access.
⚠ No rate-limit details are provided, so agent retry behavior may need conservative throttling.

Alternatives

TickTick web/app UI Direct TickTick REST/Open API integration using your own backend Community/non-MCP TickTick integrations (if available) or building a small REST-to-tool layer Other MCP connectors for task/productivity platforms

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for ticktick-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-03-30.