Clickup vs Workix MCP
A side-by-side look at the Clickup and Workix MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clickup for workplace & productivity work as a local process; choose Workix MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clickup when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Choose Workix MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
WORKIX_API, WORKIX_AGENT_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 49/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | WORKIX_APIWORKIX_AGENT_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 52 | 13 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Clickup | View Workix MCP |
Tools & capabilities
Clickup tools
No tool names declared yet. Check the project README from the listing page.
Workix MCP 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.
Clickup
{
"mcpServers": {
"clickup-2": {
"command": "npx",
"args": [
"-y",
"@taazkareem/clickup-mcp-server@latest"
]
}
}
}
Workix MCP
{
"mcpServers": {
"mcp-54": {
"command": "npx",
"args": [
"-y",
"@workix/mcp"
],
"env": {
"WORKIX_API": "YOUR_WORKIX_API_HERE",
"WORKIX_AGENT_KEY": "YOUR_WORKIX_AGENT_KEY_HERE"
}
}
}
}
Frequently asked questions
Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. Workix MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Clickup for workplace & productivity work and Workix MCP 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.
Clickup has no declared pricing — check the project's own site. Workix MCP has no declared pricing — check the project's own site. 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 clickup-2 and mcp-54 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clickup has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 52 GitHub stars. Workix MCP has 47/100 (Fair) with 0 views, 0 installs and 13 GitHub stars.