API Gateway vs Terminal MCP Server
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). Terminal MCP Server is an MCP server published by aybelatchane. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Terminal MCP Server |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 58 799 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 Downloads/month (npm): 249 Downloads/week (npm): 41 Forks (GitHub): 6 Stars (GitHub): 21 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 | Terminal MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 44 (better) | 21 (worse) |
| Pulls (Docker Hub) (differs) | 58 799 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 6 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/api-gateway) | On your machine (mcp-server-terminal) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 2, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/rflpazini/mcp-api-gateway | github.com/aybelatchane/mcp-server-terminal |
| Changes in the last 7 days | 0 | 0 |
| 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
API Gateway
A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.
Terminal MCP Server
MCP server for AI agents to interact with terminal applications. Think Playwright for terminals.
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-gatewayTerminal MCP Server As a local MCP server: npm package
claude mcp add --transport stdio mcp-server-terminal -- npx -y mcp-server-terminalCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Terminal MCP Server 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 Terminal MCP Server asks for
DISPLAYRUST_LOG
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: API Gateway · What it can do: Terminal MCP Server · 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.