Install
$ agentstack add mcp-lydakis-mcpx ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
mcpx
Turn MCP servers into composable CLIs.
mcpx # list servers
mcpx # list tools
mcpx ... # call a tool
Tool names match exactly what each server exposes. Tool-call output passes through unchanged (text or JSON), so you can pipe, redirect, or parse with jq.
Quick Start
brew tap lydakis/mcpx
brew install --cask mcpx
Install the general mcpx skill for your agent (recommended on day one):
mcpx skill install
Add extra links as needed:
mcpx skill install --claude-link
mcpx skill install --kiro-link
mcpx skill install --openclaw-link
Optionally write/update a managed mcpx guidance block in your global AGENTS file:
mcpx skill install --guidance
mcpx skill install --guidance --claude-link
mcpx skill install --guidance --kiro-link
mcpx skill install --guidance --openclaw-link
mcpx skill install --guidance --guidance-text "Prefer mcpx when MCP work benefits from CLI composition."
If you already use MCP in Cursor, Claude Code, Cline, Codex, or Kiro, mcpx auto-discovers those server configs.
mcpx github search-repositories --query=mcp | jq -r '.items[:3][].full_name'
No existing configs? Point mcpx at any MCP endpoint and start calling tools immediately:
mcpx https://docs.mcp.cloudflare.com/mcp
mcpx https://docs.mcp.cloudflare.com/mcp search_cloudflare_documentation --query="durable objects alarms"
Every tool gets schema-aware --help for free:
mcpx https://docs.mcp.cloudflare.com/mcp search_cloudflare_documentation --help
Going Deeper
Adding Servers
mcpx add bootstraps config from install links, manifest URLs, direct MCP endpoints, or local manifest files:
mcpx add https://mcp.deepwiki.com/mcp
mcpx deepwiki read_wiki_structure --repoName=modelcontextprotocol/specification
Added servers persist in ~/.config/mcpx/config.toml. You can also write entries by hand:
[servers.github]
command = "npx"
args = ["-y", "@modelcontextprotocol/server-github"]
env = { GITHUB_TOKEN = "${GITHUB_TOKEN}" }
default_cache_ttl = "30s"
Ephemeral Sources
Any source you pass directly (without mcpx add) runs ephemerally for the daemon's lifetime: no config written, nothing to clean up.
mcpx
mcpx --help
mcpx ...
Caching
Cache tool responses with --cache=, or force fresh calls with --no-cache:
mcpx deepwiki read_wiki_structure --repoName=modelcontextprotocol/specification --cache=5m
mcpx deepwiki read_wiki_structure --repoName=modelcontextprotocol/specification --no-cache
Set per-server defaults with default_cache_ttl in config.
Command Shims
Install a local passthrough so `` works as a standalone command:
mcpx shim install github
github search-repositories --query=mcp | jq -r '.items[:3][].full_name'
Shims land in $XDG_BIN_HOME or ~/.local/bin. Install is collision-safe: it fails if that name already resolves elsewhere in PATH.
mcpx shim install github --skill # also generate a server skill
mcpx shim list
mcpx shim remove github
Server-Specific Skills (Optional)
When you want tighter, server-specific instructions, generate a skill file for one server (written to ~/.agents/skills/mcpx- by default):
mcpx skill install github
mcpx skill install github --openclaw-link
Codex Apps
When Codex Apps are enabled and authenticated locally, mcpx exposes connected apps as regular servers:
mcpx linear
mcpx linear --help
mcpx linear ...
Auth stays with Codex. mcpx does not run OAuth flows or store third-party credentials.
Reference
Other Install Methods
npm:
npm install -g mcpx-go
PyPI:
pip install mcpx-go
Source:
go build ./...
./mcpx --version
Windows: use WSL2 and run install commands inside your Linux distro shell.
Commands
| Command | Purpose | |---------|---------| | mcpx add | Bootstrap a server config from a source | | mcpx shim install | Install a local passthrough shim | | mcpx shim remove | Remove a shim | | mcpx shim list | List installed shims | | mcpx completion | Print shell completions (bash/zsh/fish) | | mcpx skill install [] | Install built-in or server-specific skill |
mcpx add accepts --name, --header KEY=VALUE, and --overwrite. mcpx shim install accepts --skill and --skill-strict. mcpx skill install accepts --guidance, --guidance-file, and --guidance-text (--guidance follows a single --claude-link/--kiro-link/--openclaw-link target when provided).
Output Modes
--json applies to mcpx-owned surfaces only (mcpx, mcpx , mcpx --help). Tool-call output passes through unmodified.
Use -v to include per-server origin metadata. Combine with --json for machine-readable output including config paths.
Exit Codes
| Code | Meaning | |------|---------| | 0 | Success | | 1 | Tool error (MCP isError) | | 2 | Usage error | | 3 | Internal error |
MCP Smoke Tests
Validate any server quickly:
mcpx # list tools
mcpx --json # machine-readable
mcpx -v # full descriptions
mcpx --help # inspect schema
mcpx --help --json
echo $? # check exit code
More Examples
mcpx --json
mcpx github --json
mcpx github -v
mcpx github search-repositories --help --json
mcpx add "cursor://anysphere.cursor-deeplink/mcp/install?name=postgres&config=..."
mcpx add https://mcp.deepwiki.com/mcp
mcpx https://mcp.deepwiki.com/mcp
mcpx https://mcp.deepwiki.com/mcp read_wiki_structure --repoName=modelcontextprotocol/specification
mcpx add https://mcp.devin.ai/mcp --name deepwiki --header "Authorization=Bearer \${DEEPWIKI_API_KEY}"
mcpx skill install
Manual Config
If auto-discovery finds nothing, create ~/.config/mcpx/config.toml directly. For fallback setups, include -y for npx:
[servers.browser-tools]
command = "npx"
args = ["-y", "@agentdeskai/browser-tools-mcp@1.1.0"]
Development
QA
make check # test + vet + build
make qa-core # Go gates + core smoke/integration matrix
make qa-extended # CLI contract + wrapper packaging checks
make qa # full QA matrix (core + extended)
Benchmarks
Benchmarks are manual (not part of CI):
make perf
./scripts/perf_bench.sh # compare against baseline
make perf-loop # warm CLI throughput (500 calls)
./scripts/perf_cli_loop.sh
For summarized comparisons: go install golang.org/x/perf/cmd/benchstat@latest
Versioning
Local builds show mcpx dev. Tagged releases show the tag (for example mcpx v0.1.0) via GoReleaser ldflags.
Release
Tag pushes matching v* trigger the release workflow. GoReleaser publishes artifacts and updates lydakis/homebrew-mcpx. Notarization uses standard Apple Developer and App Store Connect secrets.
Docs
- [design](docs/design.md)
- [usage](docs/usage.md)
- [release](docs/release.md)
- [roadmap](docs/roadmap.md)
License
[MIT](LICENSE)
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lydakis
- Source: lydakis/mcpx
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.