Ext Ops Panel
Open dashboard
Comparison

Zen 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.

Zen is an MCP server published by BeehiveInnovations. 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

Where each is published
MarketplaceZenusage-panel
Docker MCP Catalog Listed
Version: sha256:02cbe1d325db
Forks (GitHub): 1 036
Pulls (Docker Hub): 34 967
Stars (Docker Hub): 0
Stars (GitHub): 11 792
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

Zen vs usage-panel
FactZenusage-panelno longer listed ·
Marketplaces that list it (differs)10
Stars (GitHub) (differs)11 7926
Pulls (Docker Hub) (differs)34 967No figure on Docker Hub
Forks (GitHub) (differs)1 0365
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/zen)On your machine (github:fschmutz/claude-usage-panel#v3.10.1)
Transport (differs)stdioNot stated
Tools it declares (differs)18Not published
Environment variables it asks for (differs)4, secrets among them: 4Not published
Parts of the bundle (differs)Not a bundle1
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/beehiveinnovations/zen-mcp-servergithub.com/fschmutz/claude-usage-panel
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-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.

  • claude-usage

    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…

    by christian-oudard · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-stats

    See your Claude Usage. And in what Projects, how many of your tokens are used.

    by Albschu · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • Usage Limits

    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…

    by ridelink0 · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • ai-adoption

    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…

    by Jeroen Van Hautte · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • mine

    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…

    by anipotts · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • claude-prospector

    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…

    by glitchwerks · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Zen

In its own words, on Docker MCP Catalog:

Bridges multiple AI models and CLIs, enabling orchestrated workflows across Claude Code, Gemini CLI, Codex CLI, and other AI development tools.

usage-panel

In its own words, on Community GitHub marketplaces:

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

Zen As a local MCP server: Docker image

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENROUTER_API_KEY=<YOUR_OPENROUTER_API_KEY>" --env "XAI_API_KEY=<YOUR_XAI_API_KEY>" --transport stdio zen -- docker run -i --rm -e GEMINI_API_KEY -e OPENAI_API_KEY -e OPENROUTER_API_KEY -e XAI_API_KEY mcp/zen

Requires: GEMINI_API_KEY (secret), OPENAI_API_KEY (secret), OPENROUTER_API_KEY (secret), XAI_API_KEY (secret)

usage-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: Zen · 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.

Where the data comes from: how the catalog is built