wmux-orchestrator vs GitHub
wmux-orchestrator is a plugin bundle for AI coding tools published by amirlehmam. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-27. 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: 0.1.1 Forks (GitHub): 3 Stars (GitHub): 11 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.3 Forks (GitHub): 5 233 Stars (GitHub): 33 981 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:250bc6ce7078 Forks (GitHub): 5 233 Stars (GitHub): 33 981 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 | wmux-orchestrator | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 11 (worse) | 33 981 (better) |
| Forks (GitHub) (differs) | 3 (worse) | 5 233 (better) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 4 | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/amirlehmam/wmux-orchestrator | github.com/github/github-mcp-server |
| Changes in the last 7 days (differs) | 2 | 3 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
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
wmux-orchestrator
Multi-agent task orchestration for Claude Code. Decomposes complex development tasks into parallel Claude Code agents coordinated through dependency-aware waves with visual terminal panes and automated review. Works standalone with native subagents or with wmux for visible agent panes. Features include dependency-aware wave planning, file zone enforcement per worker to prevent conflicts, and post-orchestration automated review with auto-fix.
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
wmux-orchestrator As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install wmux-orchestrator@claude-community
GitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of wmux-orchestrator publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of wmux-orchestrator publish no settings it asks for, so we do not compare settings.
What it can do: wmux-orchestrator · What it can do: GitHub · 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 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.