Ext Ops Panel
Open dashboard
Comparison

API Gateway vs team

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). team is a plugin bundle for AI coding tools published by dstoic. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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 Gatewayteam
Docker MCP Catalog Listed
Version: sha256:9cc67b4a037f
Forks (GitHub): 12
Pulls (Docker Hub): 58 684
Stars (Docker Hub): 6
Stars (GitHub): 44
Not marked · First seen
Not listed
Community marketplace digital-stoic-org/agent-skills Not listed Listed
Version: 0.9.0
Forks (GitHub): 7
Stars (GitHub): 20
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 team
FactAPI Gatewayteam
Marketplaces that list it11
Stars (GitHub) (differs)44 (better)20 (worse)
Pulls (Docker Hub) (differs)58 684No figure on Docker Hub
Forks (GitHub) (differs)12 (better)7 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/api-gateway)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)2Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle3
Licence (differs)Not statedMIT
Repository (differs)github.com/rflpazini/mcp-api-gatewaygithub.com/digital-stoic-org/agent-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-16

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.

team

In its own words, on Community GitHub marketplaces:

Coordination protocol for running a fleet of named Claude Code agents in parallel under one human: delegate one mandate at a time (brief), report back on a stop condition (report), hand off state at context limits (relay) — one skill per machine arrow, SendMessage the only transport. No skill reads the protocol at runtime: the mandate carries its own contract, so all three run in windows with no context to spare without reading anything at all, and a window that has never seen the plugin still behaves correctly. Context is under the human's control on both sides: read_first closes what a delegate opens before it starts, deliverable puts its findings on disk so reports and relay packets carry pointers rather than content, and a relay hands its successor the role lines that land it in READY instead of straight back into the work.

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

team As a Claude Code plugin

Claude Code
/plugin marketplace add digital-stoic-org/agent-skills
/plugin install team@digital-stoic-marketplace

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

Tools each declares

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

Settings each asks for

The marketplaces of team publish no settings it asks for, so we do not compare settings.

What it can do: API Gateway · What it can do: team · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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