API Gateway vs wmux-orchestrator
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). wmux-orchestrator is a plugin bundle for AI coding tools published by amirlehmam. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 58 618 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.1 Forks (GitHub): 3 Stars (GitHub): 11 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 | API Gateway | wmux-orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 44 (better) | 11 (worse) |
| Pulls (Docker Hub) (differs) | 58 618 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/api-gateway) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Hooks it runs (differs) | Not published | 4 |
| Parts of the bundle (differs) | Not a bundle | 9 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/rflpazini/mcp-api-gateway | github.com/amirlehmam/wmux-orchestrator |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
API Gateway
A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.
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.
How to run each
API Gateway As a local MCP server: Docker image
claude mcp add --transport stdio mcp-api-gateway -- docker run -i --rm mcp/api-gateway
wmux-orchestrator As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install wmux-orchestrator@claude-community
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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: API Gateway · What it can do: wmux-orchestrator · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.