team-orchestrator vs MCP Task Orchestrator
team-orchestrator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
team-orchestrator is a plugin bundle for AI coding tools published by choiszt. No marketplace we read lists it any more. 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-20. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MCP Task Orchestrator | |
|---|---|---|
| Community marketplace choiszt/team-orchestrator | Removed on 2026-10-19 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 4 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 | team-orchestratorno longer listed · | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 4 | 209 |
| Forks (GitHub) (differs) | 0 | 25 |
| 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) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/choiszt/team-orchestrator | github.com/jpicklyk/task-orchestrator |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of team-orchestrator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Tenant-isolated AI teams that plan work, coordinate tasks, recall approved context, and return evidence-backed results
-
Standalone Markdown-only Agent Team plugin for Claude Code and Codex. Coordination happens through ordinary Markdown files in the current project: agent-team/ ├──…
-
Shared task wall, memory, reports, channels and Dashboard for Claude Code and Codex; Claude Code plugin installation and an independent Codex adapter
-
Use this agent for optimizing human-agent collaboration workflows and analyzing workflow efficiency. This agent specializes in identifying bottlenecks, streamlining processes, and…
-
Flow turns Claude into a project partner who manages your backlog. Say "park this for later," and it queues the idea. Say "what's next?" and it finds the highest-priority ready…
-
agent-tasks io.github.keshrath/agent-tasks
Pipeline task management for AI agents - stages, dependencies, artifacts, claiming
What each says it does
team-orchestrator
Analyzes tasks to decide whether an Agent Team is needed, designs team structure with clear file ownership, and generates standardized team prompts.
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
team-orchestrator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of team-orchestrator publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of team-orchestrator publish no settings it asks for, so we do not compare settings.
What it can do: team-orchestrator · 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.