In-depth architectural comparison of the Dida MCP and Weeek 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
Dida MCP
Workplace & Productivity · Local stdio
Quality: 43/100 (Fair) | Auth: OAuth 2.0
Weeek MCP
Workplace & Productivity · Local stdio
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Dida MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Weeek MCP 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 Dida MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: DIDA_CLIENT_ID, DIDA_CLIENT_SECRET, DIDA_REDIRECT_URI.
Primary tools included: 13 MCP tools for Dida365, Project creation, lookup, and deletion, Task creation, updates, completion, and deletion.
Dida365 (TickTick China) MCP server for AI-powered task management. 13 tools for projects, tasks, tags, and habits with OAuth 2.0 authentication. Compatible with OpenClaw, Claude Desktop, and any MCP client.
Local MCP server for Weeek (stdio transport) — read-only by default, opt-in write tools.
Dida MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Weeek MCP belongs to Workplace & Productivity using local stdio subprocess. Select Dida MCP when you need capabilities focused on workplace & productivity and Weeek MCP when you require tools for workplace & productivity.