SuperCLI — 10,000 Tools, One Binary, Zero Configuration

Every developer has been here: you need a specific CLI tool — convert JSON to CSV, resize an image, check an SSL certificate, format a date. You Google it, find a npm package or a Go binary, install it, use it once, and never touch it again.

Now multiply that by every developer on your team. Everyone has their own toolbox, their own scripts, their own "I know there is a tool for that somewhere." Knowledge fragments, onboarding slows down, and the same utility gets built three times across three repos.

SuperCLI solves this by being the last CLI you install — a single binary that gives you access to 10,000+ tools. Zero configuration, no package manager, no npm install.

One CLI to Rule Them All

The idea is simple: sc is a single entry point. Every tool in the ecosystem is a plugin. Need to convert JSON to YAML?

sc json yaml < data.json

Need a QR code?

sc qr "https://intrane.fr"

Need random UUIDs?

sc uuid

No installs, no flags to memorize, no "which package has this utility." It just works.

Zero Configuration Means It

Most CLI ecosystems require setup. Package managers, PATH modifications, environment variables, configuration files. SuperCLI requires none of that. Download the binary, run sc, start using tools.

Under the hood, SuperCLI discovers plugins from a registry. The first time you run a tool, it downloads and caches it. Every subsequent call is instant. You never think about where tools come from — they are just there.

Why This Matters for Teams

When every developer on your team runs the same sc, you get:

• Shared vocabulary — "pipe it through sc json pretty" instead of "I used jq but you might need to install it first"
• Onboarding in seconds — new hire downloads one binary, not a README of prerequisites
• CI-ready — the same tools work in your pipelines without extra setup
• Auditable — every tool is versioned, every call is deterministic

The Plugin Ecosystem

Tools range from the mundane (base64 encode/decode, date formatting, math) to the powerful (Markdown to PDF, SQL formatting, OpenAPI validation, network scanning). The plugin system is language-agnostic — any compiled binary or script wrapped in a simple manifest becomes a SuperCLI plugin.

If your team has internal tools, they belong in SuperCLI. One sc deploy-staging is better than a tribal-knowledge shell alias that half the team does not have.

Open Source, Self-Hostable

SuperCLI is MIT-licensed. The registry is public by default, but you can run your own private registry for internal tools. No SaaS, no API keys, no vendor lock-in. Just sc and a catalog of tools that grows every week.

SuperCLI on GitHub — 39 stars and growing. Try it in your terminal today.

Next in this series: Self-Hosted Analytics — why I built what Google Analytics won't give you.