Ticktick MCP vs Process Street MCP Server
A side-by-side look at the Ticktick MCP and Process Street MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ticktick MCP for workplace & productivity work as a local process; choose Process Street MCP Server for workplace & productivity. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ticktick MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_REDIRECT_URI, TICKTICK_USERNAME, TICKTICK_PASSWORD.
Choose Process Street MCP Server when
- You need dedicated capabilities in the Workplace & Productivity domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 41/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | API key required | OAuth 2.0 |
| Pricing | Free | Paid service |
| Required env vars | TICKTICK_CLIENT_IDTICKTICK_CLIENT_SECRETTICKTICK_REDIRECT_URITICKTICK_USERNAMETICKTICK_PASSWORD | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 66 | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Ticktick MCP | View Process Street MCP Server |
Tools & capabilities
Ticktick MCP tools
No tool names declared yet. Check the project README from the listing page.
Process Street MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ticktick MCP
{
"mcpServers": {
"jen6-ticktick-mcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/jen6/ticktick-mcp.git",
"ticktick-mcp"
],
"env": {
"TICKTICK_CLIENT_ID": "YOUR_TICKTICK_CLIENT_ID_HERE",
"TICKTICK_CLIENT_SECRET": "YOUR_TICKTICK_CLIENT_SECRET_HERE",
"TICKTICK_REDIRECT_URI": "YOUR_TICKTICK_REDIRECT_URI_HERE",
"TICKTICK_USERNAME": "YOUR_TICKTICK_USERNAME_HERE",
"TICKTICK_PASSWORD": "YOUR_TICKTICK_PASSWORD_HERE"
}
}
}
}
Process Street MCP Server
No confirmed install command for Process Street MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Ticktick MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Process Street MCP Server belongs to Workplace & Productivity and uses an install path we have not confirmed yet. Pick Ticktick MCP for workplace & productivity work and Process Street MCP Server for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Process Street MCP Server has no confirmed install command yet — follow its own setup instructions.
Ticktick MCP is listed as free. Auth: api key required. Process Street MCP Server is listed as a paid service. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add jen6-ticktick-mcp and process-street-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ticktick MCP has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 66 GitHub stars. Process Street MCP Server has 43/100 (Fair) with 2 views, 0 installs and 1 GitHub stars.