API Gateway vs io.github.singleflo/evolution-api-mcp
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.singleflo/evolution-api-mcp is an MCP server published by singleflo. 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 |   API Gateway |  io.github.singleflo/evolution-api-mcp |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 58 363 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 151 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.singleflo/evolution-api-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 44 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 58 363 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/api-gateway) | Remote server (evolution-mcp.singleflo.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 11, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/rflpazini/mcp-api-gateway | github.com/singleflo/evolution-api-mcp |
| 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
API Gateway
A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.
io.github.singleflo/evolution-api-mcp
Operate one Evolution API (WhatsApp) instance: chats, history, sending, groups, settings.
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-gatewayio.github.singleflo/evolution-api-mcp As a remote MCP server
claude mcp add --transport http evolution-api-mcp https://evolution-mcp.singleflo.com/mcpRequires: EVOLUTION_API_URL, EVOLUTION_INSTANCE_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.singleflo/evolution-api-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Only API Gateway asks for
API_1_HEADER_AUTHORIZATIONAPI_1_NAMEAPI_1_SWAGGER_URL
Only io.github.singleflo/evolution-api-mcp asks for
EVOLUTION_API_URLEVOLUTION_INSTANCE_TOKEN (secret)EVOLUTION_MCP_ALLOWEVOLUTION_MCP_ALLOW_IRREVERSIBLEEVOLUTION_MCP_DEFAULT_DELAY_MSEVOLUTION_MCP_DENYEVOLUTION_MCP_DOWNLOAD_DIREVOLUTION_MCP_FILE_ROOTSEVOLUTION_MCP_MAX_WRITES_PER_MINUTEEVOLUTION_MCP_TIMEZONEEVOLUTION_MCP_TOOLSETS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: API Gateway · What it can do: io.github.singleflo/evolution-api-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.