Quick Start
Get from zero to calling MCP tools in under 2 minutes.
Option A: Import Existing Config
If you already have MCP servers configured (.mcp.json from Claude Code, etc.):
bash
mcpx initDetected .mcp.json
Imported 3 servers:
serena uvx (daemon)
seq-thinking npx
filesystem npx
Created .mcpx/config.ymlDone. Skip to Use It.
Option B: Manual Config
Create .mcpx/config.yml in your project root:
yaml
servers:
serena:
command: uvx
args:
- --from
- git+https://github.com/oraios/serena
- serena
- start-mcp-server
- --project
- "$(mcpx.project_root)"
transport: stdio
daemon: trueOr add a global server at ~/.mcpx/config.yml:
yaml
servers:
sequential-thinking:
command: npx
args: ["-y", "@modelcontextprotocol/server-sequential-thinking"]
transport: stdioUse It
Discover servers
bash
mcpx list
# serena uvx (daemon)
# sequential-thinking npxDiscover tools
bash
mcpx list serena -vShows every tool with all its flags — full discovery in one call.
Call a tool
bash
mcpx serena search_symbol --name "UserAuth"Get help for a tool
bash
mcpx serena search_symbol --helpShows flag names, types, required markers, descriptions, and defaults — all auto-generated from the MCP schema.
Health check
bash
mcpx ping serena
# serena: ok (21 tools, 47ms)JSON output
bash
mcpx serena search_symbol --name "Auth" --jsonPipe and compose
bash
mcpx serena search_symbol --name "Auth" | jq -r '.[].file' | xargs codeWhat Just Happened
mcpxread your config to find the server- For daemon servers: spawned the server once, connected via unix socket
- For direct servers: spawned a subprocess, did the MCP handshake
- Translated your CLI flags into a JSON-RPC
tools/callrequest - Printed the result to stdout
The AI agent does exactly the same thing — it just runs these commands via Bash.
Next Steps
- AI Agent Setup — integrate with Claude Code or Cursor
- Configuration — two-level config, server options
- Daemon Mode — keep heavy servers warm