Clickup vs Cueapi MCP
A side-by-side look at the Clickup and Cueapi 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 Cueapi 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 Cueapi MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You want tools like
cueapi_create_cue, cueapi_list_cues, cueapi_get_cue.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 49/100 · Fair | 53/100 · Good |
| 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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 52 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 15 |
| Full listing | View Clickup | View Cueapi MCP |
Tools & capabilities
Clickup tools
No tool names declared yet. Check the project README from the listing page.
Cueapi MCP tools 15
cueapi_create_cueCreate a recurring (cron) or one-time (`at`) cuecueapi_list_cuesList cues, filter by statuscueapi_get_cueFetch details for a single cuecueapi_fire_cueFire an existing cue immediately, optional payload overridecueapi_update_cueUpdate a cue's mutable fields (name, schedule, callback, payload, etc.)cueapi_pause_cuePause a cue so it stops firingcueapi_resume_cueResume a paused cuecueapi_delete_cueDelete a cue permanentlycueapi_list_executionsList historical executions, filter by cue/statuscueapi_get_executionFetch a single execution by ID, with state + outcomecueapi_list_claimable_executionsList unclaimed worker executions, filter server-side by task/agentcueapi_claim_executionAtomically claim a specific execution for processing- +3 more on 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"
]
}
}
}
Cueapi MCP
{
"mcpServers": {
"mcp-7": {
"command": "npx",
"args": [
"-y",
"@cueapi/mcp"
]
}
}
}
Frequently asked questions
Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. Cueapi MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Clickup for workplace & productivity work and Cueapi 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. Cueapi 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-7 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. Cueapi MCP has 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars.