Third-Party Ecosystem
Community-built tools that extend Claude Code. Every tool verified against its public repository.
By the Numbers
Tool Browser
No tools match your filters.
Recommendations by Persona
| Persona | Recommended Tools | Rationale |
|---|---|---|
| Solo developer | ccusage + claude-code-viewer | Cost awareness + session history review |
| Small team (2-5) | ccusage + Conductor or multiclaude | Cost tracking + parallel development |
| Enterprise | ccusage (MCP) + Entire CLI | Programmatic cost data + audit trails |
| Python-centric | ccburn + Claude Chic | Native Python ecosystem tools |
| Multi-agent user | Toad or Conductor | Unified agent management |
| Config-heavy setup | claude-code-config + AIBlueprint | TUI config management + scaffolding |
Related: MCP vs CLI Decision Guide
Not sure whether to use MCP servers or CLI tools for a given integration? The decision guide covers four key questions, a 15-row guidance table by situation, and token cost analysis.
MCP vs CLI — Which to use? →Known Gaps
As of March 2026, community tooling has notable missing pieces:
Visual Skills Editor
No GUI for creating or editing .claude/skills/ — must edit YAML/Markdown manually.
Visual Hooks Editor
No GUI for managing hooks in settings.json — requires JSON editing.
Unified Admin Panel
No single dashboard combining config, sessions, cost, and MCP management.
Per-MCP-Server Profiler
No way to measure token cost attributable to each MCP server individually.
Cross-Platform Config Sync
No tool syncs Claude Code config across machines — manual copy of ~/.claude/ required.
Session Replay ✅ Filled
Entire CLI (launched Feb 2026) provides rewindable checkpoints with full context replay.