Back to browse
GitHub Repository

Turn MCP servers into composable CLIs.

52 starsGo

MCPX – Turn any MCP server into a composable CLI for agents

by ldkge·Feb 28, 2026·2 points·1 comment

AI Analysis

●●SolidBig BrainNiche Gem

MCP servers as shell pipes—clever abstraction, but only matters if you're already in the MCP ecosystem.

Strengths
  • Schema-aware --help and native flag surface from MCP inputSchema reduces friction significantly.
  • Explicit exit-code mapping and pass-through tool output enable genuine Unix composition (jq, pipes).
  • Thoughtful design for agent workflows: stdio + HTTP transports, optional caching, Codex Apps integration.
Weaknesses
  • Audience is narrow: requires already using MCP servers and agent frameworks (OpenClaw, Claude Code).
  • No evidence of adoption beyond proof-of-concept; MCP ecosystem itself is still emerging.
Target Audience

Agent developers (OpenClaw, Claude Code), CLI tool builders, and engineers integrating MCP servers into shell-first workflows.

Similar To

ModelContextProtocol (MCP itself) · Claude Code native tool integration

Post Description

I built MCPX: https://github.com/lydakis/mcpx

Core idea: MCPX turns MCP servers into Unix-composable commands for agent workflows. It is primarily for agents that are shell-first, and secondarily useful for humans running tools directly.

For me, a practical use case is OpenClaw: OpenClaw can call `mcpx` like any normal CLI and use MCP servers immediately, without implementing custom MCP transport/auth plumbing in OpenClaw itself. This also fits well with Codex Apps mode, where connected apps can be exposed as MCP servers through the same command contract.

Command contract: - mcpx - mcpx <server> - mcpx <server> <tool>

Design choices: - schema-aware `--help` (inputs + declared outputs) - native flag surface from MCP `inputSchema` - pass-through tool output for normal shell composition (`jq`, `head`, pipes) - explicit exit mapping (`0/1/2/3`) - stdio + HTTP server support - optional caching - `mcpx add` for bootstrapping server config from install links/manifests/endpoints

Examples: - mcpx github search-repositories --help - mcpx github search-repositories --query=mcp - echo '{"query":"mcp"}' | mcpx github search-repositories

Install: - brew tap lydakis/mcpx && brew install --cask mcpx - npm i -g mcpx-go - pip install mcpx-go

I would love feedback on command UX, schema/flag edge cases, and where this should stop vs expand.

Similar Projects

Developer Tools●●Solid

Unix-style pipeline composition for MCP tool calls

The project implements a sandboxed, server-side 'shell' that pipes MCP tool calls together so agents return only final outputs — a smart way to save tokens and handle datasets too large for LLM context. The repo includes a demo video, tests, and a real shell_engine/mcp_client implementation, but it's a focused infra play for the MCP ecosystem and will matter most to teams building agent platforms rather than general devs.

Niche GemBig BrainShip It
kantord
303mo ago