Ext Ops Panel
Open dashboard
Comparison

PomoDash vs Weeeking

PomoDash is an MCP server published by DannyyTv. Marketplaces we read that list it: 1 (Docker MCP Catalog). Weeeking is an MCP server published by OniVe. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
MarketplacePomoDashWeeeking
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.6.0
Downloads/month (npm): 1 105
Downloads/week (npm): 1 105
Forks (GitHub): 0
Stars (GitHub): 0
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 Weeeking
FactPomoDashWeeeking
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Pulls (Docker Hub) (differs)9 564No figure on Docker Hub
Forks (GitHub)00
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/pomodash)On your machine (weeeking)
Transportstdiostdio
Tools it declares (differs)14Not published
Environment variables it asks for (differs)2, secrets among them: 113, secrets among them: 2
Licence (differs)MITNot stated
Repository (differs)github.com/dannyytv/pomodash-mcp-servergithub.com/onive/weeeking
Changes in the last 7 days (differs)02
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.

Weeeking

In its own words, on Official MCP Registry:

MCP server for Weeek with full public API coverage: tasks, projects, CRM, time tracking.

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)

Weeeking As a local MCP server: npm package

Claude Code
claude mcp add --env "WEEEK_API_TOKEN=<YOUR_WEEEK_API_TOKEN>" --env "WEEEK_TOKEN=<YOUR_WEEEK_TOKEN>" --transport stdio weeeking -- npx -y weeeking

Requires: WEEEK_API_TOKEN (secret), WEEEK_TOKEN (secret)

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

Tools each declares

The marketplaces of Weeeking 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 Weeeking asks for

  • READ_ONLY
  • WEEEK_ALLOW_ACTIONS
  • WEEEK_API_TOKEN (secret)
  • WEEEK_BASE_URL
  • WEEEK_DENY_ACTIONS
  • WEEEK_DISABLE_KEYCHAIN
  • WEEEK_LANG
  • WEEEK_LOG
  • WEEEK_MAX_RESPONSE_CHARS
  • WEEEK_PROFILE
  • WEEEK_RPS
  • WEEEK_RPS_BURST
Show the remaining 1
  • WEEEK_TOKEN (secret)

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

What it can do: PomoDash · What it can do: Weeeking · 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