Clickup vs Weeek MCP
A side-by-side look at the Clickup and Weeek 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 Weeek 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 Weeek 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:
WEEEK_ACCESS_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 49/100 · Fair | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | WEEEK_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 52 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Clickup | View Weeek MCP |
Tools & capabilities
Clickup tools
No tool names declared yet. Check the project README from the listing page.
Weeek 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"
]
}
}
}
Weeek MCP
{
"mcpServers": {
"weeek-mcp": {
"command": "npx",
"args": [
"-y",
"weeek-mcp"
],
"env": {
"WEEEK_ACCESS_TOKEN": "YOUR_WEEEK_ACCESS_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Clickup is categorized under Workplace & Productivity and uses a local stdio subprocess. Weeek MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Clickup for workplace & productivity work and Weeek 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. Weeek MCP has no declared pricing — check the project's own site. Auth: api key required. 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 weeek-mcp 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. Weeek MCP has 45/100 (Fair) with 5 views, 0 installs and 0 GitHub stars.