Ext Ops Panel
Open dashboard
Comparison

PomoDash vs MCP Task Orchestrator

PomoDash is an MCP server published by DannyyTv. Marketplaces we read that list it: 1 (Docker MCP Catalog). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-15. 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
MarketplacePomoDashMCP Task Orchestrator
Docker MCP Catalog Listed
Version: sha256:bb9539723f2a
Forks (GitHub): 0
Pulls (Docker Hub): 9 562
Stars (Docker Hub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: sha256:eab0bb62611a
Forks (GitHub): 24
Stars (GitHub): 207
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 3.16.0
Forks (GitHub): 24
Stars (GitHub): 207
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 MCP Task Orchestrator
FactPomoDashMCP Task Orchestrator
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 (worse)207 (better)
Pulls (Docker Hub) (differs)9 562No figure on Docker Hub
Forks (GitHub) (differs)0 (worse)24 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/pomodash)On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0)
Transportstdiostdio
Tools it declares (differs)1442
Environment variables it asks for (differs)2, secrets among them: 17, secrets among them: 0
LicenceMITMIT
Repository (differs)github.com/dannyytv/pomodash-mcp-servergithub.com/jpicklyk/task-orchestrator
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.

MCP Task Orchestrator

In its own words, on Official MCP Registry:

Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

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)

MCP Task Orchestrator As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0

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

Tools each declares

Only PomoDash declares

  • create_category
  • create_note
  • create_note_for_project
  • create_note_for_task
  • create_task_for_project
  • delete_note
  • list_categories
  • list_note_references
  • list_notes
  • list_tasks
  • update_note

Only MCP Task Orchestrator declares

  • add_section
  • add_template_section
  • apply_template
  • bulk_create_sections
  • bulk_delete_sections
  • bulk_update_sections
  • bulk_update_tasks
  • create_dependency
  • create_feature
  • create_project
  • create_template
  • delete_dependency
Show the remaining 27
  • delete_feature
  • delete_project
  • delete_section
  • delete_template
  • disable_template
  • enable_template
  • feature_to_markdown
  • get_feature
  • get_overview
  • get_project
  • get_sections
  • get_task
  • get_task_dependencies
  • get_template
  • list_templates
  • project_to_markdown
  • reorder_sections
  • search_features
  • search_projects
  • search_tasks
  • task_to_markdown
  • update_feature
  • update_project
  • update_section
  • update_section_metadata
  • update_section_text
  • update_template_metadata

Both declare

  • create_task
  • delete_task
  • update_task

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only PomoDash asks for

  • POMODASH_API_KEY (secret)
  • POMODASH_API_URL

Only MCP Task Orchestrator asks for

  • AGENT_CONFIG_DIR
  • DATABASE_PATH
  • LOG_FILE
  • LOG_LEVEL
  • MCP_HTTP_PORT
  • MCP_TRANSPORT
  • USE_FLYWAY

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

What it can do: PomoDash · What it can do: MCP Task Orchestrator · 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