Ext Ops Panel
Open dashboard
Comparison

PomoDash vs Google Tasks MCP Server

PomoDash is an MCP server published by DannyyTv. Marketplaces we read that list it: 1 (Docker MCP Catalog). Google Tasks MCP Server is an MCP server published by ebmurha. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplacePomoDashGoogle Tasks MCP Server
Docker MCP Catalog Listed
Version: sha256:bb9539723f2a
Forks (GitHub): 0
Pulls (Docker Hub): 9 564
Stars (Docker Hub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 126
Downloads/week (PyPI): 39
Forks (GitHub): 0
Stars (GitHub): 2
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

PomoDash vs Google Tasks MCP Server
FactPomoDashGoogle Tasks MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Pulls (Docker Hub) (differs)9 564No figure on Docker Hub
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pomodash)On your machine (google-tasks-mcp)
Transportstdiostdio
Tools it declares (differs)14Not published
Environment variables it asks for (differs)2, secrets among them: 15, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/dannyytv/pomodash-mcp-servergithub.com/ebmurha/google-tasks-mcp
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

PomoDash

In its own words, on Docker MCP Catalog:

Connect your AI assistant to PomoDash for seamless task and project management.

Google Tasks MCP Server

In its own words, on Official MCP Registry:

Manage Google Tasks from MCP-compatible AI clients.

How to run each

PomoDash As a local MCP server: Docker image

Claude Code
claude mcp add --env "POMODASH_API_KEY=<YOUR_POMODASH_API_KEY>" --transport stdio pomodash -- docker run -i --rm -e POMODASH_API_KEY mcp/pomodash

Requires: POMODASH_API_KEY (secret)

Google Tasks MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REDIRECT_URI=<YOUR_GOOGLE_REDIRECT_URI>" --transport stdio google-tasks-mcp -- uvx google-tasks-mcp

Requires: GOOGLE_CLIENT_ID (secret), GOOGLE_CLIENT_SECRET (secret), GOOGLE_REDIRECT_URI

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

Tools each declares

The marketplaces of Google Tasks MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only PomoDash asks for

  • POMODASH_API_KEY (secret)
  • POMODASH_API_URL

Only Google Tasks MCP Server asks for

  • DB_PATH
  • DEFAULT_TASKLIST
  • GOOGLE_CLIENT_ID (secret)
  • GOOGLE_CLIENT_SECRET (secret)
  • GOOGLE_REDIRECT_URI

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

What it can do: PomoDash · What it can do: Google Tasks MCP Server · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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