In-depth architectural comparison of the Ticktick MCP and MCP Server 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 MCP
Workplace & Productivity · Local stdio
Quality: 41/100 (Fair) | Auth: API Key required
MCP Server
Workplace & Productivity · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Ticktick MCP if you need specialized Workplace & Productivity tools running via a local process. Choose MCP Server if your workspace requires Workplace & Productivity 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 MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_REDIRECT_URI, TICKTICK_USERNAME, TICKTICK_PASSWORD.
Primary tools included: Task creation, update, deletion, completion, and movement, Subtask creation by linking tasks, Retrieve uncompleted, completed (by date range), and filtered tasks.
TickTick MCP server. Built upon the ticktick-py library, it offers significantly improved filtering capabilities.
The document publishing layer for AI tools. Convert markdown to formatted documents for Google Docs, Word, Slack, OneNote, Email, and Plain Text with 62 templates.
Ticktick MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, MCP Server belongs to Workplace & Productivity using local stdio subprocess. Select Ticktick MCP when you need capabilities focused on workplace & productivity and MCP Server when you require tools for workplace & productivity.