Engineering vs Task-Orchestrator
Engineering is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Task-Orchestrator is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 317 Stars (GitHub): 29 279 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | Engineering | Task-Orchestrator |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 29 279 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 317 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (task-orchestrator-mcp-three.vercel.app/api/mcp) |
| Transport (differs) | Not stated | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 20 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/anthropics/knowledge-work-plugins | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Engineering
Streamline engineering workflows — standups, code review, architecture decisions, incident response, and technical documentation. Works with your existing tools or standalone.
Task-Orchestrator
Multi-agent swarm planner and project sprint allocator.
How to run each
Engineering As a Claude Code plugin
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install engineering@knowledge-work-pluginsTask-Orchestrator As a remote MCP server
claude mcp add --transport sse task-orchestrator https://task-orchestrator-mcp-three.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Engineering · What it can do: 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.