Ext Ops Panel
Open dashboard
Comparison

API Gateway vs M3 Memory

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). M3 Memory is an MCP server published by skynetcmd. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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

Where each is published
MarketplaceAPI GatewayM3 Memory
Docker MCP Catalog Listed
Version: sha256:9cc67b4a037f
Forks (GitHub): 12
Pulls (Docker Hub): 58 532
Stars (Docker Hub): 6
Stars (GitHub): 44
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.10.7.1
Downloads/month (PyPI): 5 393
Downloads/week (PyPI): 982
Forks (GitHub): 4
Stars (GitHub): 28
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

API Gateway vs M3 Memory
FactAPI GatewayM3 Memory
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)44 (better)28 (worse)
Pulls (Docker Hub) (differs)58 532No figure on Docker Hub
Forks (GitHub) (differs)12 (better)4 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/api-gateway)On your machine (m3-memory)
Transportstdiostdio
Tools it declares (differs)2Not published
Environment variables it asks for (differs)3, secrets among them: 06, secrets among them: 0
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle22
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/rflpazini/mcp-api-gatewaygithub.com/skynetcmd/m3-memory
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

In its own words, on Docker MCP Catalog:

A universal MCP (Model Context Protocol) server to integrate any API with Claude Desktop using only Docker configurations.

M3 Memory

In its own words, on Official MCP Registry:

Local-first memory — 100+ tools, 99.2% LongMemEval-S retrieval@8, hybrid search, GDPR, no cloud.

How to run each

API Gateway As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio mcp-api-gateway -- docker run -i --rm mcp/api-gateway

M3 Memory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio m3-memory -- uvx m3-memory

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of M3 Memory publish no list of tools, so we do not compare tools.

Settings each asks for

Only API Gateway asks for

  • API_1_HEADER_AUTHORIZATION
  • API_1_NAME
  • API_1_SWAGGER_URL

Only M3 Memory asks for

  • LLM_ENDPOINTS_CSV
  • M3_AUTO_INSTALL
  • M3_CONFIG_ROOT
  • M3_EMBED_FALLBACK_URL
  • M3_EMBED_GGUF
  • M3_ENGINE_ROOT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: API Gateway · What it can do: M3 Memory · 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. 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.

Where the data comes from: how the catalog is built