Google Tasks vs Clickup
A side-by-side look at the Google Tasks 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 Google Tasks 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 Google Tasks when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_TASKS_CLIENT_SECRET, GOOGLE_TASKS_TOKEN_PATH, GOOGLE_TASKS_OAUTH_PORT. - You want tools like
google_tasks_list_tasklists, google_tasks_get_tasklist, google_tasks_create_tasklist.
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 | GOOGLE_TASKS_CLIENT_SECRETGOOGLE_TASKS_TOKEN_PATHGOOGLE_TASKS_OAUTH_PORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 53 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 14 | Not listed |
| Full listing | View Google Tasks | View Clickup |
Tools & capabilities
Google Tasks tools 14
google_tasks_list_tasklistsgoogle_tasks_get_tasklistgoogle_tasks_create_tasklistgoogle_tasks_update_tasklistgoogle_tasks_delete_tasklistgoogle_tasks_list_tasksgoogle_tasks_get_taskgoogle_tasks_create_taskgoogle_tasks_update_taskgoogle_tasks_complete_taskgoogle_tasks_reopen_taskgoogle_tasks_delete_task- +2 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.
Google Tasks
{
"mcpServers": {
"google-tasks": {
"command": "npx",
"args": [
"-y",
"-p",
"@girmmy/google-tasks-mcp-server",
"google-tasks-mcp-auth"
],
"env": {
"GOOGLE_TASKS_CLIENT_SECRET": "YOUR_GOOGLE_TASKS_CLIENT_SECRET_HERE",
"GOOGLE_TASKS_TOKEN_PATH": "YOUR_GOOGLE_TASKS_TOKEN_PATH_HERE",
"GOOGLE_TASKS_OAUTH_PORT": "YOUR_GOOGLE_TASKS_OAUTH_PORT_HERE"
}
}
}
}
Clickup
{
"mcpServers": {
"clickup-2": {
"command": "npx",
"args": [
"-y",
"@taazkareem/clickup-mcp-server@latest"
]
}
}
}
Frequently asked questions
Google Tasks is categorized under Workplace & Productivity and uses a local stdio subprocess. Clickup belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Google Tasks 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.
Google Tasks 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 google-tasks and clickup-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Tasks has a quality signal of 55/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Clickup has 49/100 (Fair) with 2 views, 0 installs and 53 GitHub stars.