Ext Ops Panel
Open dashboard
Comparison

API Gateway vs Context Optimizer (CCO)

API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). Context Optimizer (CCO) is a plugin bundle for AI coding tools published by Egor Fedorov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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 GatewayContext Optimizer (CCO)
Docker MCP Catalog Listed
Version: sha256:9cc67b4a037f
Forks (GitHub): 12
Pulls (Docker Hub): 58 858
Stars (Docker Hub): 6
Stars (GitHub): 44
Not marked · First seen
Not listed
Community marketplace egorfedorov/claude-context-optimizer Not listed Listed
Version: 5.0.2
Forks (GitHub): 10
Stars (GitHub): 117
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 Context Optimizer (CCO)
FactAPI GatewayContext Optimizer (CCO)
Marketplaces that list it11
Stars (GitHub) (differs)44 (worse)117 (better)
Pulls (Docker Hub) (differs)58 858No figure on Docker Hub
Forks (GitHub) (differs)12 (better)10 (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
Hooks it runs (differs)Not published6
Parts of the bundle (differs)Not a bundle15
Licence (differs)Not statedMIT
Repository (differs)github.com/rflpazini/mcp-api-gatewaygithub.com/egorfedorov/claude-context-optimizer
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-17

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.

Context Optimizer (CCO)

In its own words, on Community GitHub marketplaces:

See what Claude costs you and spend less of it. In chat: hand a long chat over to a new one, digest long documents, set up Projects, check tokens, sharpen prompts. In Claude Code: a live line with context, cost, plan limits and the cache countdown; Haiku 5.5 subagents for reading and test runs; /cco audit of your own transcripts. Local, no telemetry.

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

Context Optimizer (CCO) As a Claude Code plugin

Claude Code
/plugin marketplace add egorfedorov/claude-context-optimizer
/plugin install context-optimizer@cco

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

Tools each declares

The marketplaces of Context Optimizer (CCO) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Context Optimizer (CCO) publish no settings it asks for, so we do not compare settings.

What it can do: API Gateway · What it can do: Context Optimizer (CCO) · 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