Clihub
Install CliHub so your agent can wrap existing CLI binaries like jq, ffmpeg, or gh as stdio MCP tools without writing a custom server for each command.
Overview
CliHub is a Build-phase MCP server pattern that wraps any CLI binary via `ch mcp wrap` so coding agents can call familiar command-line tools over stdio MCP.
What is this MCP server?
- `ch mcp wrap <tool> --stdio` exposes any CLI binary as an MCP server
- npm package @clihub/cli with positional args: mcp, wrap, and required tool name
- Discover CLI tools and recipes through the CliHub workflow
- Beta 0.1.0-beta.0 stdio transport for local agent hosts
- Examples in schema: jq, ffmpeg, gh as wrappable tools
- Package version 0.1.0-beta.0 on npm as @clihub/cli
- Three required positional runtime arguments: mcp, wrap, tool name
- Optional --stdio named flag for stdio transport
What problem does it solve?
You keep re-implementing thin MCP servers around jq, ffmpeg, or gh when you only need your agent to run the CLI you already use.
Who is it for?
Indie builders who standardize on CLIs and want fast MCP exposure during Build.
Skip if: Teams that need hosted HTTP MCP, rich auth flows, or production SLAs beyond local stdio wrap.
What do I get? / Deliverables
After installing @clihub/cli and wrapping a binary, your agent gains MCP tools backed by that CLI without a custom server repo per tool.
- stdio MCP server surface for a chosen CLI binary
- Agent-callable tools mapped from wrapped command behavior
- Faster integration path versus hand-written MCP per CLI
Recommended MCP Servers
Journey fit
CliHub is used while building and extending the product stack—turning proven CLIs into agent-callable tools—rather than during idea research or post-launch analytics. Integrations is the right shelf because the core job is bridging host agents to external binaries via MCP wrap, not authoring UI or docs.
How it compares
CLI-to-MCP wrap utility, not a curated cloud API marketplace.
Common Questions / FAQ
Who is CliHub for?
Developers and solo builders who want agents to invoke existing CLI binaries through MCP without authoring a dedicated server for each tool.
When should I use CliHub?
Use it in Build when integrating agent workflows with command-line utilities you already run locally, such as JSON processing, media, or GitHub CLI tasks.
How do I add CliHub to my agent?
Install @clihub/cli from npm, configure your MCP client to run `ch mcp wrap <binary> --stdio` (for example `ch mcp wrap jq --stdio`), and register the resulting stdio server in Claude Code or Cursor.