Turn an API description into a CLI your agent can use in Claude Code, Codex or any app that speaks MCP. One command gives you the CLI with an MCP server, and a test for every operation of the API. When the template improves, its upgrade command merges the change into the CLI you already edited.
From PokeAPI's published description to 102 commands, a real answer and a working MCP server took 16 seconds with an empty pnpm store and 12 with a warm one, not counting npx's own download. Nine of WireCat's own CLIs are made from it, among them hubspot-cli and ydisk, which are on its latest version through its upgrade.
npx @wirecat/cli-template new poke-cli --preset generic --owner example --sign-in none \
--spec-url https://raw.githubusercontent.com/PokeAPI/pokeapi/d19c710/openapi.yml
cd poke-cli && pnpm install && pnpm generate
node dist/bin/poke.js personal api pokemon-get --id pikachu --json=name,height,weight
node dist/bin/poke.js personal mcp add claude-codePut your own GitHub name in --owner and the address of your service's description in --spec-url, JSON or YAML.
--preset generic answers the questions only WireCat's own tools need, and any flag you give wins. Without it, new
asks for every missing answer and never guesses one.
flowchart LR
spec["API description<br/>OpenAPI 3 or Swagger 2.0, JSON or YAML,<br/>or Google Discovery"] -->|new, generate| cli["Your CLI<br/>one command per operation"]
cli --> mcp["MCP server"]
cli --> skill["Agent skill"]
mcp --> apps["Claude Code, Codex<br/>or any app that speaks MCP"]
skill --> apps
poke-cli/
├── spec/poke/openapi.yaml the API description, and where it came from
├── src/generated/ types, schemas and a manifest of every operation
├── src/commands/ the api group, the sign-in and your own commands
├── src/api.test.ts every operation sent to a strict fake of the API
├── skills/ the agent skill, with pages for the API
├── .github/workflows/ CI, the release and a monthly check
└── bin/release publishes each version to npm through GitHub
- Your agent gets the API the day you start.
poke personal mcp serveserves every command to an agent over MCP, andpoke skill installteaches Claude Code, Codex or Gemini CLI how to use the tool. - The token stays in the OS keyring, under a profile you name, such as
personalorwork. No profile is ever assumed: a command without one stops and lists the profiles.
- It keeps up after you edit.
upgrademerges each template change into your CLI file by file, and asks before it touches a file you changed. A one-time generator leaves you to copy its later fixes by hand. - One set of commands, three ways in. The same commands are the CLI, the MCP tools and the skill, so what you test is what the agent runs.
- You decide what an agent may do. Each profile sets
allow,readonlyordenyper command and per API operation. An operation that deletes needs its own permission key, and the api group refuses to build without one. - Tests come with the API.
src/api.test.tssends every operation to a fake built from the description, which refuses a request the description does not allow. It also checks that a denied delete stops before anything is sent. - Google APIs too. Besides OpenAPI 3 and Swagger 2.0 it reads Google's Discovery documents.
Checked on the tools' own pages in November 2026. "Not documented" means the page does not say.
| What it makes | For agents | After you edit it | Tests in the project | License | |
|---|---|---|---|---|---|
| cli-template | A TypeScript CLI project | MCP server (stdio and HTTP) and a skill, from the same commands | upgrade merges template changes |
One per operation, against a strict fake | Apache-2.0 |
| Speakeasy | A Go CLI, and an MCP server as a separate product | Agent mode for Claude Code, Cursor and others | Not documented | Contract tests, offered as a separate product | Vendor service, the CLI generator labelled alpha in its docs |
| openapi-mcp-generator | A TypeScript MCP server | MCP only | --force writes over your edits |
Not documented | MIT |
FastMCP from_openapi |
An MCP server built at run time, in Python | MCP only | No code is generated | Not documented | Apache-2.0 |
| api2cli | A Commander.js CLI and a skill, written by a Claude Code skill | A Claude Code skill | A one-time result | None shown | MIT |
What cli-template does not do. It is Node and TypeScript only (Node 22.16 or 24 and later, with pnpm), and it
builds no single binary. The api group calls one base URL, and its generator stops on a keyword it does not
understand, so some descriptions need a patch with its reason before they generate. The CLI signs in with a token: OAuth is yours to wire up, from cli-core's oauth module. The skeleton keeps
no data of its own and has no search.
new --spec-url <url> downloads the description (https only, at most 20 MB), puts its servers into the hosts the
CLI may reach, and records the address and a hash in spec/<command>/provenance.json. pnpm generate then writes
one command per operation, its permissions, its tests and the skill's API pages.
When the generator stops on part of the description, it names the place. Add a patch with its reason in
scripts/spec-model.ts, or set what to treat as a delete in scripts/generate.ts, as the
OpenAPI guide shows. When the service changes its API, pnpm spec:sync
downloads it again and pnpm generate follows.
Run npx @wirecat/cli-template upgrade in your CLI, with a clean git working tree. For each file the template
changed it offers to merge the change, take the template's file, skip it or show the diff. --dry-run lists what
each file would get and writes nothing. The files that are yours from the start, such as your commands in
src/commands/, README.md and package.json, are never touched. The details are in the
kit reference.
npx skills add WireCatLabs/cli-templateThis installs the api-to-cli skill for Claude Code, Codex and other agents. Ask your agent for a CLI for
a service, and it finds the description, runs new, fixes what the generator stops on, and wires the MCP server. It
never runs the CLI against your account without asking. WireCat's own CLIs use the longer
new-cli skill, which also keeps the research and reviews in WireCat's repositories.
A CLI made outside WireCat publishes under its own npm scope, such as @example/poke-cli. new --preset generic
sets it up for that, with its own MCP Registry name and its own monthly CI run, and no recorded live check before a
release. bin/setup-github creates the
repository, and bin/release --first publishes the first version from your computer. The steps, with npm trusted
publishing, are in Publishing outside WireCat.
new copies this repository into your CLI. Its command word is the placeholder clidev, which new replaces with
yours. It is not cli-dev, the developer tool in cli-base. new writes a fresh README for each new CLI, so this
page never reaches one.
To work on the template itself:
pnpm install
pnpm build
node dist/bin/clidev.js doctorThe skeleton's own pages describe clidev as a user sees it: install,
use it, settings, commands,
when something goes wrong and security. The working rules for people
and agents are in AGENTS.md, how new and upgrade read this repository is in
kit/DEVELOPING.md, and pnpm release:check runs every check before a release.
Report a vulnerability privately as SECURITY.md says. The changes are in CHANGELOG.md.

