MCP Task Orchestrator vs Markdown Pipeline
MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Markdown Pipeline is an MCP server published by markdown-pipeline. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  Markdown Pipeline |
|---|---|---|
| Official MCP Registry | Listed Version: 4.0.0 Forks (GitHub): 25 Stars (GitHub): 214 Not marked · First seen |
Listed Version: 0.1.20 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:eab0bb62611a Forks (GitHub): 25 Stars (GitHub): 214 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 | Markdown Pipeline |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 214 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 25 (better) | 0 (worse) |
| Last release (differs) | 2026-11-09 (better) | 2026-11-09 (worse) |
| Where it runs (differs) | On your machine (ghcr.io/jpicklyk/task-orchestrator:4.0.0) | On your machine (mdpipeline) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 42 | Not published |
| Environment variables it asks for (differs) | 46, secrets among them: 0 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jpicklyk/task-orchestrator | github.com/markdown-pipeline/markdown-pipeline |
| Changes in the last 7 days (differs) | 4 | 3 |
| First seen (differs) | 2026-10-11 | 2026-11-01 |
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
Workflow discipline for AI agents: work items, gates, role-scoped tool profiles and runs
Markdown Pipeline
Your team's Jira as clean Markdown files, kept current for your AI agent. Local and read-only.
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:4.0.0Markdown Pipeline As a local MCP server: PyPI package
claude mcp add --transport stdio mdpipeline -- uvx mdpipeline --install-method registry mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Markdown Pipeline publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Markdown Pipeline publish no settings it asks for, so we do not compare settings.
What it can do: MCP Task Orchestrator · What it can do: Markdown Pipeline · 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.