MCP Task Orchestrator vs darwin-memo
MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). darwin-memo is an MCP server published by rogermsc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  MCP Task Orchestrator |  darwin-memo |
|---|---|---|
| Official MCP Registry | Listed Version: 3.16.0 Forks (GitHub): 25 Stars (GitHub): 209 Not marked · First seen |
Listed Version: 0.7.1 Downloads/month (PyPI): 252 Downloads/week (PyPI): 39 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:eab0bb62611a Forks (GitHub): 25 Stars (GitHub): 209 Not marked · First seen |
Not listed |
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 | MCP Task Orchestrator | darwin-memo |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 209 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 25 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) | On your machine (darwin-memo) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 0 | 1, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jpicklyk/task-orchestrator | github.com/rogermsc/darwin-memo |
| 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
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
darwin-memo
Self-curating agent memory kept honest by survival-based selection over measured outcomes.
How to run each
MCP Task Orchestrator As a local MCP server: Docker image
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0darwin-memo As a local MCP server: PyPI package
claude mcp add --transport stdio darwin-memo -- uvx --with "darwin-memo[mcp]" darwin-memo mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of darwin-memo publish no list of tools, so we do not compare tools.
Settings each asks for
Only MCP Task Orchestrator asks for
AGENT_CONFIG_DIRDATABASE_PATHLOG_FILELOG_LEVELMCP_HTTP_PORTMCP_TRANSPORTUSE_FLYWAY
Only darwin-memo asks for
DARWIN_MEMO_PATH
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: MCP Task Orchestrator · What it can do: darwin-memo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.