Ext Ops Panel
Open dashboard
Comparison

Google Tasks MCP vs io.github.taazkareem/clickup

Google Tasks MCP is an MCP server published by A1-x-Tech. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.taazkareem/clickup is an MCP server published by taazkareem. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGoogle Tasks MCPio.github.taazkareem/clickup
Official MCP Registry Listed
Version: 1.0.0
Downloads/month (npm): 593
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.12.12
Downloads/month (npm): 11 296
Downloads/week (npm): 733
Forks (GitHub): 7
Stars (GitHub): 53
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.14.6
Downloads/month (npm): 11 296
Downloads/week (npm): 733
Forks (GitHub): 7
Stars (GitHub): 53
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Google Tasks MCP vs io.github.taazkareem/clickup
FactGoogle Tasks MCPio.github.taazkareem/clickup
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)53 (better)
Forks (GitHub) (differs)0 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp-google-tasks)On your machine (@taazkareem/clickup-mcp-server)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)8, secrets among them: 34, secrets among them: 2
Licence (differs)Not statedProprietary
Repository (differs)github.com/a1-x-tech/mcp-google-tasksgithub.com/taazkareem/clickup-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Google Tasks MCP

In its own words, on Official MCP Registry:

MCP server for the Google Tasks API: task lists, subtasks, due dates, complete and move tasks.

io.github.taazkareem/clickup

In its own words, on Official MCP Registry:

Premium AI integration. Tasks, lists, docs, folders, time. 50+ tools. Instant setup.

How to run each

Google Tasks MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_TASKS_ACCESS_TOKEN=<YOUR_GOOGLE_TASKS_ACCESS_TOKEN>" --env "GOOGLE_TASKS_CLIENT_SECRET=<YOUR_GOOGLE_TASKS_CLIENT_SECRET>" --env "GOOGLE_TASKS_REFRESH_TOKEN=<YOUR_GOOGLE_TASKS_REFRESH_TOKEN>" --transport stdio mcp-google-tasks -- npx -y mcp-google-tasks

Requires: GOOGLE_TASKS_ACCESS_TOKEN (secret), GOOGLE_TASKS_CLIENT_SECRET (secret), GOOGLE_TASKS_REFRESH_TOKEN (secret)

io.github.taazkareem/clickup As a local MCP server: npm package

Claude Code
claude mcp add --env "CLICKUP_API_KEY=<YOUR_CLICKUP_API_KEY>" --env "CLICKUP_MCP_LICENSE_KEY=<YOUR_CLICKUP_MCP_LICENSE_KEY>" --env "CLICKUP_TEAM_ID=<YOUR_CLICKUP_TEAM_ID>" --transport stdio clickup -- npx -y @taazkareem/clickup-mcp-server

Requires: CLICKUP_API_KEY (secret), CLICKUP_MCP_LICENSE_KEY (secret), CLICKUP_TEAM_ID

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only Google Tasks MCP asks for

  • GOOGLE_TASKS_ACCESS_TOKEN (secret)
  • GOOGLE_TASKS_API_BASE
  • GOOGLE_TASKS_CLIENT_ID
  • GOOGLE_TASKS_CLIENT_SECRET (secret)
  • GOOGLE_TASKS_MAX_RETRIES
  • GOOGLE_TASKS_OAUTH_PORT
  • GOOGLE_TASKS_REFRESH_TOKEN (secret)
  • GOOGLE_TASKS_TIMEOUT_MS

Only io.github.taazkareem/clickup asks for

  • CLICKUP_API_KEY (secret)
  • CLICKUP_MCP_LICENSE_KEY (secret)
  • CLICKUP_TEAM_ID
  • DOCUMENT_SUPPORT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Google Tasks MCP · What it can do: io.github.taazkareem/clickup · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built