Turn published docs into runnable commands

Your API docs, now a terminal command.

docstar-cli reads a DocStar docs site, discovers its published modules and endpoints, and installs each one as a real CLI command — required parameters and all.

How it works

From docs site to terminal command in four steps

No SDKs to install, no request-building boilerplate — the CLI does that for you.

1. Point it at your docs

Run init against any DocStar site.

zsh — init
$ docstar-cli init docs.msg91.com

2. Pick your modules

An interactive checklist shows every published module — pick what you need.

zsh — modules
Payments (payments) Auth (auth)

3. List what's installed

Every module gets its own list command.

zsh — list
$ docstar-cli payments list

4. Call it directly

Pass flags, or leave them out and get prompted for what's required.

zsh — charge
$ docstar-cli payments charge \ --MY_SECRET_KEY "sk_live_..."

docs.msg91.com → module.json → ~/.docstar/ → real CLI command → live API call

Under the hood

Built for how APIs are actually documented

Zero-boilerplate calls

Method, URL, headers, and body are all derived from the published endpoint — you just supply the values.

Interactive by default

Skip a required flag and the CLI will ask for it, so a command works even before you've read the docs.

Local-first

Modules are saved to ~/.docstar after install — no round-trip to the docs site to run a command.

Organized by module

Every module gets its own command namespace, plus a list command to browse it.

Safe by design

Only published, non-deleted endpoints are exposed — never drafts, internal notes, or raw credentials.

Always in sync

Re-run init any time to pick up newly published endpoints.

Under the hood

Local-first, after one lookup

init fetches each endpoint's contract once. Every call after that runs entirely from your machine.

Reads your docs site once

init calls your DocStar site's module.json endpoints to fetch the collection's modules and each one's endpoint contract — method, URL, headers, body, and parameter names.

Caches contracts locally

Every contract is saved to disk. Running a command builds the real HTTP request from that local copy — no network round-trip to the docs site.

Generates real commands

Each endpoint becomes an actual file on disk, so a command like docstar-cli payments charge is a real, inspectable CLI command — not a dynamic dispatcher.

Use it from an AI client

Run docstar-cli mcp to expose every installed endpoint as an MCP tool. Agents can call your published APIs directly — no shell copy-paste required.

Each endpoint becomes one tool named <cli-name>__<module>__<command>, with its parameters exposed in the tool schema. Run docstar-cli init first so there's at least one installed module for it to expose.

claude_desktop_config.json
{ "mcpServers": { "docstar": { "command": "docstar-cli", "args": ["mcp"] } } }

Install it and try it on your own docs

Works with any DocStar-published documentation site.

View source on GitHubnpm

docstar-cli — built on oclif

Publish docs, then call them from the terminal

Ship your API docs on DocStar, then install docstar-cli and turn every published endpoint into a command.

No credit card required. Setup in minutes.