mcp2cli connects to an MCP server, introspects its tool catalog, and generates a complete CLI. Each tool becomes a subcommand. Each parameter becomes a flag. Single binary. Zero config.
MCP servers are great for agents. Now they're great for humans too.
Point it at a server. Get a CLI. Every MCP tool becomes a subcommand with typed flags and help text.
Connects to any MCP server over stdio, discovers its full tool catalog, and maps every tool to a subcommand automatically.
JSON Schema types become typed CLI flags. Strings, numbers, booleans, arrays, and enums are all handled. Descriptions become help text.
Produces standalone bash scripts that route subcommands back through mcp2cli exec. Add to PATH and use anywhere.
Every command supports --json for structured output that pipes into jq, gripe, or any other tool. Human-friendly tables by default.
Server tools change over time. Run mcp2cli update to re-introspect and regenerate the CLI in place. Always in sync.
Init multiple servers, list them, remove them. Each gets its own config manifest and generated script. No conflicts.
MCP servers were built for agents. Now you can test, debug, and explore them without spinning up a framework.
Pipe MCP tool output into jq, gripe, or any Unix tool. JSON output makes MCP servers first-class shell citizens.
Generated scripts are standalone bash. Check them into your repo, run them in CI, use them in Makefiles. No runtime needed.
One command to init. The generated CLI is ready immediately.