API Gateway vs @cocal/google-calendar-mcp
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). @cocal/google-calendar-mcp is an MCP server published by @cocal. Marketplaces we read that list it: 1 (npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:9cc67b4a037f Forks (GitHub): 12 Pulls (Docker Hub): 59 645 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.8.1 Downloads/month (npm): 36 840 Downloads/week (npm): 9 959 Forks (GitHub): 336 Stars (GitHub): 1 206 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 | @cocal/google-calendar-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 44 (worse) | 1 206 (better) |
| Pulls (Docker Hub) (differs) | 59 645 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (worse) | 336 (better) |
| Last release (differs) | Not published | 2026-10-30 |
| Where it runs (differs) | On your machine (mcp/api-gateway) | On your machine (@cocal/google-calendar-mcp) |
| 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 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/rflpazini/mcp-api-gateway | github.com/nspady/google-calendar-mcp |
| 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.
@cocal/google-calendar-mcp
Google Calendar MCP Server with extensive support for calendar management
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@cocal/google-calendar-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of @cocal/google-calendar-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of @cocal/google-calendar-mcp publish no settings it asks for, so we do not compare settings.
What it can do: API Gateway · What it can do: @cocal/google-calendar-mcp · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.