jamdesk vs MCP Task Orchestrator
jamdesk is a plugin bundle for AI coding tools published by jamdesk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-19. 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 |  jamdesk |  MCP Task Orchestrator |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.20 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.16.0 Forks (GitHub): 24 Stars (GitHub): 209 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:eab0bb62611a Forks (GitHub): 24 Stars (GitHub): 209 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 | jamdesk | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 3 (worse) | 209 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 24 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (jamdesk.com/docs/_mcp) | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) |
| Transport (differs) | Streamable HTTP | 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) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/jamdesk/jamdesk-claude-plugin | github.com/jpicklyk/task-orchestrator |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 23 h ago | no remote endpoint we check |
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
jamdesk
Gives Claude deep knowledge of the Jamdesk documentation platform — 25+ MDX components with full props and examples, complete docs.json configuration schema, 8 navigation patterns, 19 CLI commands, and writing standards. Claude loads only the reference sections relevant to each task, keeping context efficient.
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
jamdesk As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install jamdesk@claude-communityMCP 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.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only jamdesk has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of jamdesk publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of jamdesk publish no settings it asks for, so we do not compare settings.
What it can do: jamdesk · What it can do: MCP Task Orchestrator · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/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.