cogni-consult vs MCP Task Orchestrator
cogni-consult is a plugin bundle for AI coding tools published by Stephan de Haas. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-25. 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 | |
|---|---|---|
| Community marketplace cogni-work/insight-wave | Listed Version: 0.1.130 Forks (GitHub): 2 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.16.0 Forks (GitHub): 25 Stars (GitHub): 209 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:eab0bb62611a Forks (GitHub): 25 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 | cogni-consult | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 13 (worse) | 209 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 25 (better) |
| 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 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 14 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/cogni-work/insight-wave | github.com/jpicklyk/task-orchestrator |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 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
cogni-consult
Consulting engagement orchestrator where action fields are the work-breakdown-structure containers for every deliverable: each deliverable runs its own design-thinking loop (empathize→define→ideate→prototype→test), acting stakeholder personas challenge the work in their own voice, and one cogni-knowledge base per engagement is the central research tool that compounds across all deliverables.
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
cogni-consult As a Claude Code plugin
/plugin marketplace add cogni-work/insight-wave
/plugin install cogni-consult@insight-waveMCP 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.
Tools each declares
The marketplaces of cogni-consult publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of cogni-consult publish no settings it asks for, so we do not compare settings.
What it can do: cogni-consult · What it can do: MCP Task Orchestrator · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.