TaScan vs Clickup
A side-by-side look at the TaScan and Clickup MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TaScan for workplace & productivity work as a local process; choose Clickup 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 TaScan when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You want tools like
tascan_list_projects, tascan_get_project, tascan_create_project.
Choose Clickup when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 55/100 · Good | 49/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 52 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 41 | Not listed |
| Full listing | View TaScan | View Clickup |
Tools & capabilities
TaScan tools 41
tascan_list_projectsList all projects in the organizationtascan_get_projectGet details of a specific projecttascan_create_projectCreate a new projecttascan_update_projectUpdate project name, location, status, datestascan_delete_projectDelete a project and all its contentstascan_list_eventsList all events within a projecttascan_get_eventGet event details including taskstascan_create_eventCreate a new event in a projecttascan_update_eventUpdate event name, description, modestascan_delete_eventDelete an event and all its taskstascan_list_tasksList all tasks in an eventtascan_get_taskGet task details including completions; each completion carries `photo_url` (raw storage path) + `photo_signed_url` (fetchable, ~1h, `null` when no photo)- +29 more on the listing page
Clickup 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.
TaScan
{
"mcpServers": {
"tascan": {
"command": "npx",
"args": [
"-y",
"tascan-mcp"
]
}
}
}
Clickup
{
"mcpServers": {
"clickup-2": {
"command": "npx",
"args": [
"-y",
"@taazkareem/clickup-mcp-server@latest"
]
}
}
}
Frequently asked questions
TaScan is categorized under Workplace & Productivity and uses a local stdio subprocess. Clickup belongs to Workplace & Productivity and uses a local stdio subprocess. Pick TaScan for workplace & productivity work and Clickup 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.
TaScan has no declared pricing — check the project's own site. Clickup 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 tascan and clickup-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TaScan has a quality signal of 55/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Clickup has 49/100 (Fair) with 2 views, 0 installs and 52 GitHub stars.