io.github.girmmy/google-tasks vs io.github.mholzen/workflowy
io.github.girmmy/google-tasks is an MCP server published by girmmy. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mholzen/workflowy is an MCP server published by mholzen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
| Marketplace |  io.github.girmmy/google-tasks |  io.github.mholzen/workflowy |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (npm): 314 Downloads/week (npm): 60 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.8.1 Forks (GitHub): 7 Stars (GitHub): 72 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
| Fact | io.github.girmmy/google-tasks | io.github.mholzen/workflowy |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 72 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 7 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@girmmy/google-tasks-mcp-server) | On your machine (ghcr.io/mholzen/workflowy:0.8.1) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/girmmy/google-tasks-mcp-server | github.com/mholzen/workflowy |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
io.github.girmmy/google-tasks
Read/write Google Tasks: create, update, complete, delete, move tasks and lists, with due dates.
io.github.mholzen/workflowy
Create, update, complete nodes, search & replace with regex and dry run, usage reports, transforms
How to run each
io.github.girmmy/google-tasks As a local MCP server: npm package
claude mcp add --transport stdio google-tasks -- npx -y @girmmy/google-tasks-mcp-serverio.github.mholzen/workflowy As a local MCP server: Docker image
claude mcp add --env "WORKFLOWY_API_KEY=<YOUR_WORKFLOWY_API_KEY>" --transport stdio workflowy -- docker run -i --rm -e WORKFLOWY_API_KEY ghcr.io/mholzen/workflowy:0.8.1Requires: WORKFLOWY_API_KEY (secret)
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 io.github.girmmy/google-tasks asks for
GOOGLE_TASKS_CLIENT_SECRETGOOGLE_TASKS_OAUTH_PORTGOOGLE_TASKS_TOKEN_PATH
Only io.github.mholzen/workflowy asks for
WORKFLOWY_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.girmmy/google-tasks · What it can do: io.github.mholzen/workflowy · Compare two other plugins
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.