API Gateway vs usage-panel
usage-panel is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑21.
API Gateway is an MCP server published by rflpazini. Marketplaces we read that list it: 1 (Docker MCP Catalog). usage-panel is a plugin bundle for AI coding tools published by Falco Schmutz. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, 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): 58 902 Stars (Docker Hub): 6 Stars (GitHub): 44 Not marked · First seen |
Not listed |
| Community marketplace fschmutz/claude-usage-panel | Not listed | Removed on 2026-10-21 Version: 3.10.1 Forks (GitHub): 5 Stars (GitHub): 6 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 | usage-panelno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | 44 | 6 |
| Pulls (Docker Hub) (differs) | 58 902 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 | 5 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/api-gateway) | On your machine (github:fschmutz/claude-usage-panel#v3.10.1) |
| 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 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/rflpazini/mcp-api-gateway | github.com/fschmutz/claude-usage-panel |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of usage-panel
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Lets Claude check its own claude.ai plan quota: percent used of the session and weekly limits (including per-model weekly limits), when each resets, and where usage is on pace to…
-
See your Claude Usage. And in what Projects, how many of your tokens are used.
-
Reads how much of your 5-hour and weekly Claude Code limit is left, converts it into turns of headroom rather than a percentage, and plans the work to fit inside it. Detects plan…
-
Two skills for analyzing your Claude history. token-doctor diagnoses where your Claude Code + Cowork spend goes, including sub-agent fan-out and model mix. task-profile mines…
-
Mines every Claude Code session into a local SQLite database and provides a /mine skill with 18+ natural language query intents. Track costs, tokens, tools, projects, errors…
-
Claude Code efficiency and hygiene toolkit. Surfaces token spend across the 5h / 7d / Sonnet-7d billing windows with per-model / per-agent / per-skill attribution, and audits your…
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.
usage-panel
Ask Claude for your plan usage and switch accounts in-conversation: get_usage returns session, weekly, and per-model limits from the official Anthropic usage endpoint; waiting lists live sessions blocked on a permission prompt, a question, or idle after Stop; list_accounts / save_account / switch_account manage named Claude Code logins (PRO, PERSO) without a browser.
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-gatewayusage-panel
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 usage-panel publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of usage-panel publish no settings it asks for, so we do not compare settings.
What it can do: API Gateway · What it can do: usage-panel · 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.