In-depth architectural comparison of the Ticktick Sdk and Ticktick MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Ticktick Sdk
Other Tools and Integrations · Local stdio
Quality: 56/100 (Good) | Auth: OAuth 2.0
Ticktick MCP
Other Tools and Integrations · Local stdio
Quality: 48/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Ticktick Sdk if you need specialized Other Tools and Integrations tools running via a local process. Choose Ticktick MCP if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ticktick Sdk when:
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_ACCESS_TOKEN, TICKTICK_USERNAME, TICKTICK_PASSWORD.
Comprehensive async Python SDK for TickTick with MCP server support. Features 45 tools for tasks, projects, tags, habits, focus/pomodoro sessions, and user analytics.
MCP server for TickTick task management: create, update, complete, move, and filter tasks with field-preserving updates and completion tracking.
Category & Scope
Tools & Capabilities Breakdown
Ticktick Sdk Tools (43)
ticktick_create_tasks
Create 1-50 tasks with titles, dates, tags, etc.
ticktick_get_task
Get task details by ID
ticktick_list_tasks
List tasks (active/completed/abandoned/deleted via status filter)
ticktick_update_tasks
Update 1-100 tasks (includes column assignment)
ticktick_complete_tasks
Complete 1-100 tasks
ticktick_delete_tasks
Delete 1-100 tasks (moves to trash)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Ticktick Sdk is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Ticktick MCP belongs to Other Tools and Integrations using local stdio subprocess. Select Ticktick Sdk when you need capabilities focused on other tools and integrations and Ticktick MCP when you require tools for other tools and integrations.