MCP Task Orchestrator vs Atwork
MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Atwork is an MCP server published by atwork.so. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 | |
|---|---|---|
| Official MCP Registry | Listed Version: 3.16.0 Forks (GitHub): 25 Stars (GitHub): 209 Not marked · First seen |
Listed Version: 1.0.1 No figure published 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 | Atwork |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 209 | No figure on GitHub |
| Forks (GitHub) (differs) | 25 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) | Remote server (mcp.atwork.so/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 0 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jpicklyk/task-orchestrator | Not stated |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-20 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Atwork
Connect Claude, ChatGPT or any MCP client to your Atwork sheets, tasks, pages and dashboards.
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.0Atwork As a remote MCP server
claude mcp add --transport http workspace https://mcp.atwork.so/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Atwork publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Atwork publish no settings it asks for, so we do not compare settings.
What it can do: MCP Task Orchestrator · What it can do: Atwork · 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.