Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Wrap any CLI as a Model Context Protocol server - schema auto-inferred from --help.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cli2mcp": {
"command": "npx",
"args": [
"-y",
"cli2mcp"
]
}
}
}Run this in your terminal
claude mcp add cli2mcp -- npx -y cli2mcpThis one needs values on its command line, so copy the settings and fill them in.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cli2mcp": {
"command": "npx",
"args": [
"-y",
"cli2mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one needs values on its command line, so copy the settings and fill them in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"cli2mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cli2mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account RonieNeubauer, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.4) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Avalanche bulletins and mountain weather forecasts for any place in the Alps.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Status: v0.1 — early release. Stdio transport only. APIs may change before 1.0.
Expose any command-line binary as a Model Context Protocol tool by parsing its --help output and synthesizing a JSON Schema at startup. One command, no boilerplate.
Works with any MCP-compatible client — Claude Desktop, ChatGPT (via OpenAI Agents SDK), Cursor, Gemini CLI, Cline, Windsurf, Continue, Zed, and anything else that speaks the MCP stdio transport.
npx cli2mcp <command>
Writing an MCP server for a CLI you already have is mechanical work: instantiate the SDK, register a tool, hand-write the input schema, marshal arguments, spawn the subprocess, format the output. Roughly 80–150 lines of TypeScript per binary, repeated forever as new tools come out.
cli2mcp does it in one command. The CLI's own --help is the source of truth for the schema — if rg adds a flag tomorrow, the AI sees it tomorrow without code changes.
npm install -g cli2mcp
npx cli2mcp
Requires Node.js 22+.
cli2mcp is launched by your client as a stdio subprocess. Add an entry per CLI you want to expose.
Config file location:
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
{
"mcpServers": { "ripgrep": { "command": "npx", "args": ["-y", "cli2mcp", "rg", "--name", "ripgrep"] }, "jq": { "command": "npx", "args": ["-y", "cli2mcp", "jq"] } } }
Restart Claude Desktop after editing.
| Client | Config file | Format |
|---|---|---|
| ChatGPT (OpenAI Agents SDK) | MCPServerStdio parameter — see OpenAI Agents docs | command: "npx", args: ["-y", "cli2mcp", " "] |
| Cursor | .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) | Same mcpServers block as above |
| Cline | VS Code → Cline → MCP Settings → cline_mcp_settings.json | Same mcpServers block |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | Same mcpServers block |
| Gemini CLI | ~/.gemini/settings.json | Same mcpServers block |
| Continue | ~/.continue/config.json → experimental.modelContextProtocolServers | Same launcher |
| Zed | ~/.config/zed/settings.json → context_servers | Same launcher |
| Any stdio-capable MCP client | per the client's docs | Same launcher: npx -y cli2mcp |
Refer to each client's documentation for the exact config path on your platform — they evolve and are not guaranteed to match the table above.
Drop any of these into your client's mcpServers block (paths shown above per client). Each one wraps a popular CLI as an MCP tool an AI can call directly.
{
"mcpServers": { "ripgrep": { "command": "npx", "args": ["-y", "cli2mcp", "rg", "--name", "ripgrep", "--description", "Recursively search files with regex"] }, "jq": { "command": "npx", "args": ["-y", "cli2mcp", "jq", "--description", "Query and transform JSON via stdin"] }, "pandoc": { "command": "npx", "args": ["-y", "cli2mcp", "pandoc", "--description", "Convert documents between markup formats"] }, "sqlite3": { "command": "npx", "args": ["-y", "cli2mcp", "sqlite3", "--description", "Run SQL against a SQLite database file", "--cwd", "/path/to/safe/dir"] }, "yt-dlp": { "command": "npx", "args": ["-y", "cli2mcp", "yt-dlp", "--description", "Download media from URLs", "--cwd", "/path/to/downloads", "--timeout", "300000"] } } }
Each CLI must already be installed and on
PATH.cli2mcpdoes not install them for you.
| Approach | LOC per CLI | New flag handling | Maintenance |
|---|---|---|---|
| Hand-written MCP server (TypeScript SDK) | ~80–150 | manual schema edit | per-CLI release cycle |
| OpenAPI → MCP generators | n/a | requires an OpenAPI spec | does not cover arbitrary CLIs |
Wrapping bash / sh as a tool | ~10 | n/a — gives the AI a shell | unsafe, no schema, no sandbox |
| `cli2mcp ` | 0 | automatic at next start | none — re-reads `--help` |
The closest neighbor is FastMCP's from_openapi — it does not cover arbitrary CLI binaries. As of April 2026 there is no other published tool that turns an arbitrary --help output into a typed MCP tool in one command.
These CLIs are covered by the test suite or have been manually exercised end-to-end:
| CLI | Status | Notes |
|---|---|---|
jq | ✅ tested | help-on-stderr correctly captured; stdin piping works |
ripgrep (rg) | ✅ tested | 90+ flags inferred; args positional handled |
curl | ✅ fixture | shape extraction validated against bundled fixture |
node | ✅ integration test | end-to-end MCP handshake + tools/call |
Other POSIX-style CLIs (e.g. ffmpeg, yt-dlp, pandoc, sqlite3, imagemagick) are *expected* to work but are not yet covered by tests. Report bugs in issues.
| Help fragment | MCP property |
|---|---|
--flag | boolean |
--flag / / | string |
--flag / / | number |
--flag | string enum with choices |
| Repeatable flag | array |
| Positional args | args: array |
Reserved input stdin | string piped to subprocess stdin |
When parsing fails on an unconventional --help, cli2mcp falls back to a single variadic args positional so the tool is still usable — the model just gets a free-form argument list instead of typed flags.
cli2mcp <command> [options]
--name Tool name shown to the AI (default: ) --description Tool description shown to the AI (default: first --help line) --timeout Subprocess timeout per call (default: 60000) --cwd Working directory for subprocess (default: process.cwd()) --env Extra environment variables (repeatable) --stderr stderr handling: include → appended to tool output (default) drop → discarded error → any stderr → isError: true -h, --help Show help
Reserved input property stdin is piped to the subprocess:
{ "args": [".name"], "stdin": "{\"name\": \"cli2mcp\"}" }
cli2mcp rg
│ ├─ 1. spawn: rg --help → capture stdout + stderr ├─ 2. parse help text → CliShape { flags, positionals, description } ├─ 3. synthesize JSON Schema → inputSchema ├─ 4. register one MCP tool → name: "rg", schema: └─ 5. start stdio MCP server → await client connection
On tools/call: { args, flags, stdin? } → argv builder → execa(rg, argv, { stdin }) │ stdout (+ stderr) → content[text]
Non-zero exit → { isError: true, content: [{ type: "text", text: }] } (unless --stderr drop).
cli2mcp lets an AI agent invoke the CLIs you expose, with the arguments the agent chooses. You are responsible for what those CLIs can do on your machine.
Practical guidance:
jq, rg, pandoc are mostly safe (read-only, deterministic). curl, ffmpeg --output, sqlite3, rm, kubectl, aws are not.curl to fetch evil.example.com, an exposed rm to delete files, etc.cli2mcp provides.The schema-from-help design *reduces* the risk of malformed argv but does not eliminate the risk of misuse. Treat each exposed CLI as a delegated capability, not a sandbox.
The CLI has no `--help` flag. cli2mcp will still start with a single args positional. The AI can pass arguments freely; you lose typed flag inference.
The schema came out empty / wrong. Run cli2mcp manually and inspect the tools/list response (use npx @modelcontextprotocol/inspector). The most common cause is non-standard help formatting (no --long-form flags, columns misaligned). Open an issue with the --help output attached.
The subprocess hangs. The default 60s timeout will kill it. Raise via --timeout. If your CLI is interactive (waits for a TTY), cli2mcp cannot help — pipe input via stdin instead.
Flag not being passed. Set --stderr include (the default) and inspect the content[].text. If the flag isn't appearing in argv, the help parser failed to extract it — file an issue.
Bug reports and patches welcome. Fixtures for new CLIs (test/fixtures/help/ .txt + a shape test) are the highest-leverage contributions.
pnpm install
pnpm test # vitest pnpm typecheck # tsc --noEmit pnpm lint # biome check
If cli2mcp saved you an afternoon of writing MCP boilerplate, a star helps other people find it.
Built by Ronie Neubauer — Principal Engineer, 22+ years shipping production systems.
MIT © 2026 Ronie Neubauer.