Design vs MCP Task Orchestrator
Design is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). 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-14. 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 | ||
|---|---|---|
| Claude: knowledge-work-plugins | Listed Version: 1.2.0 Forks (GitHub): 3 361 Stars (GitHub): 29 647 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.16.0 Forks (GitHub): 24 Stars (GitHub): 207 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:eab0bb62611a 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
| Fact | Design | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 29 647 (better) | 207 (worse) |
| Forks (GitHub) (differs) | 3 361 (better) | 24 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 42 |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 0 |
| Parts of the bundle (differs) | 16 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/anthropics/knowledge-work-plugins | github.com/jpicklyk/task-orchestrator |
| 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
Design
Accelerate design workflows — critique, design system management, UX writing, accessibility audits, research synthesis, and dev handoff. From exploration to pixel-perfect specs.
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
Design As a Claude Code plugin
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install design@knowledge-work-plugins
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.0
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Design publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Design publish no settings it asks for, so we do not compare settings.
What it can do: Design · What it can do: MCP Task Orchestrator · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.