karimo-harness-engineering-agent-orchestration vs io.github.forkflux/forkflux-mcp
karimo-harness-engineering-agent-orchestration is a plugin bundle for AI coding tools published by opensesh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.forkflux/forkflux-mcp is an MCP server published by forkflux. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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 Code: claude-plugins-community | Listed Version: 4db5deb Forks (GitHub): 41 Stars (GitHub): 291 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.0 Downloads/month (PyPI): 133 Downloads/week (PyPI): 71 Forks (GitHub): 1 Stars (GitHub): 6 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 | karimo-harness-engineering-agent-orchestration | io.github.forkflux/forkflux-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 291 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 41 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (forkflux-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | Not published | 4 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/opensesh/karimo | github.com/forkflux/forkflux |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 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
karimo-harness-engineering-agent-orchestration
Harness engineering framework for Claude Code — plan mode on steroids. Product design-driven agent orchestration with sub-agents and agent teams, tuned for developers and designers shipping real features. Phased adoption from PRD execution to automated review, code review, and CI-friendly agent teams
io.github.forkflux/forkflux-mcp
Self-hosted multi-agent collaboration and audit layer for AI-assisted engineering teams
How to run each
karimo-harness-engineering-agent-orchestration As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install karimo-harness-engineering-agent-orchestration@claude-community
io.github.forkflux/forkflux-mcp As a local MCP server: PyPI package
claude mcp add --env "FORKFLUX_API_KEY=<YOUR_FORKFLUX_API_KEY>" --transport stdio forkflux-mcp -- uvx forkflux-mcp
Requires: FORKFLUX_API_KEY (secret)
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
The marketplaces of karimo-harness-engineering-agent-orchestration publish no settings it asks for, so we do not compare settings.
What it can do: karimo-harness-engineering-agent-orchestration · What it can do: io.github.forkflux/forkflux-mcp · 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 public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.