mcpx works with any MCP-compatible agent via stdio or HTTP.
The agent spawns mcpx as a subprocess. No server needed.
claude mcp add mcpx -- bunx mcpx-tools stdio mcpx.jsonOr add to .mcp.json (checked into git so your team shares the config):
{
"mcpServers": {
"mcpx": {
"command": "bunx",
"args": ["mcpx-tools", "stdio", "mcpx.json"]
}
}
}Add to ~/.cursor/mcp.json or .cursor/mcp.json:
{
"mcpServers": {
"mcpx": {
"command": "bunx",
"args": ["mcpx-tools", "stdio", "mcpx.json"]
}
}
}Add to ~/.codex/config.toml:
[mcp_servers.mcpx]
command = "bunx"
args = ["mcpx-tools", "stdio", "mcpx.json"]Point your agent's MCP config at:
bunx mcpx-tools stdio mcpx.jsonThe agent connects to a running mcpx server over the network. See deployment first.
claude mcp add-json mcpx '{"type":"http","url":"https://mcp.yourcompany.com/mcp","headers":{"Authorization":"Bearer TOKEN"}}'Or in .mcp.json:
{
"mcpServers": {
"mcpx": {
"type": "http",
"url": "https://mcp.yourcompany.com/mcp",
"headers": { "Authorization": "Bearer ${MCPX_AUTH_TOKEN}" }
}
}
}{
"mcpServers": {
"mcpx": {
"url": "https://mcp.yourcompany.com/mcp",
"headers": { "Authorization": "Bearer YOUR_TOKEN" }
}
}
}[mcp_servers.mcpx]
url = "https://mcp.yourcompany.com/mcp"
bearer_token_env_var = "MCPX_AUTH_TOKEN"