Ticktick MCP vs Hackmd MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Ticktick MCP vs Hackmd MCP
In-depth architectural comparison of the Ticktick MCP and Hackmd 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 MCP
Workplace & Productivity · Remote HTTP/SSE
Quality: 52/100 (Good) | Auth: OAuth 2.0
Hackmd MCP
Workplace & Productivity · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
Verdict Summary: Choose Ticktick MCP if you need specialized Workplace & Productivity tools running via a hosted cloud SSE transport. Choose Hackmd 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 Ticktick MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer remote streaming HTTP/SSE 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_BASE_URL, TICKTICK_TOKEN_URL.
TickTick MCP server using the official OAuth 2.0 API. Supports creating, listing, updating, completing, and deleting tasks. Includes a natural language skill for automatic task detection in Claude Cowork.
Ticktick MCP is categorized under Workplace & Productivity and uses a remote streaming HTTP/SSE transport. In contrast, Hackmd MCP belongs to Workplace & Productivity using local stdio subprocess. Select Ticktick MCP when you need capabilities focused on workplace & productivity and Hackmd MCP when you require tools for workplace & productivity.