claude-config-dashboard vs Claude Usage
claude-config-dashboard is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
claude-config-dashboard is a plugin bundle for AI coding tools published by AshtonYoon. No marketplace we read lists it any more. Claude Usage is an MCP server published by syk8015. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Claude Usage | |
|---|---|---|
| Community marketplace ashtonyoon/claude-config-dashboard | Removed on 2026-10-20 Version: 1.11.0 Forks (GitHub): 1 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | claude-config-dashboardno longer listed · | Claude Usage |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 5 | 0 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Not stated |
| Transport | Not stated | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ashtonyoon/claude-config-dashboard | github.com/syk8015/claudeusage |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
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 claude-config-dashboard
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Track Claude Code usage, rejections, and session stats in one dashboard.
-
Status line plugin for Claude Code: live view of model, context, cost, and rate limits with customizable widgets and themes.
-
Live TUI dashboard showing all active Claude Code sessions with status, latest messages, and key metrics.
-
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…
-
MCP server that orchestrates multiple Claude CLI instances as parallel workers with a real-time dashboard
-
Flightdeck observability for Claude Code sessions — streams every LLM call, tool use, and MCP event to a self-hosted dashboard.
What each says it does
claude-config-dashboard
Local web dashboard and CLI for ~/.claude config visualization — measured per-session token cost, install-vs-used gaps, and a review-first cleanup script for plugins, agents, skills, hooks, and MCP servers
Claude Usage
Measures whether your Claude subscription is paying off, from local logs. No upload.
How to run each
claude-config-dashboard
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Claude Usage
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
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: claude-config-dashboard · What it can do: Claude Usage · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.