@axiolex/mcp-gateway
v0.2.1
Published
Stdio-to-HTTP proxy for Axiolex MCP. Connects stdio-only MCP clients (Claude Desktop, Cursor, Codex) to a remote Axiolex server.
Maintainers
Readme
@axiolex/mcp-gateway
A tiny stdio-to-HTTP proxy that connects stdio-only MCP clients to a remote Axiolex server.
Why
Some MCP clients only support the stdio transport — they spawn a local subprocess and communicate over stdin/stdout. At the time of writing, this includes Claude Desktop, Cursor, and Codex. Axiolex serves MCP over HTTP at /mcp on the API server (port 9700). This proxy bridges the two: it speaks stdio to the client and HTTP to Axiolex.
The proxy is ~150 lines of JavaScript with one dependency (@modelcontextprotocol/sdk). No Python, no Redis, no ML libraries.
Install
No install needed — npx fetches and caches the package automatically:
{
"mcpServers": {
"axiolex": {
"command": "npx",
"args": ["-y", "@axiolex/mcp-gateway", "--endpoint", "http://localhost:9700/mcp"]
}
}
}Or install globally:
npm install -g @axiolex/mcp-gatewayClient config
Claude Desktop
{
"mcpServers": {
"axiolex": {
"command": "npx",
"args": [
"-y",
"@axiolex/mcp-gateway",
"--endpoint", "http://localhost:9700/mcp"
]
}
}
}Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"axiolex": {
"command": "npx",
"args": ["-y", "@axiolex/mcp-gateway", "--endpoint", "http://localhost:9700/mcp"]
}
}
}Codex
Add to ~/.codex/config.toml:
[mcp_servers.axiolex]
command = "npx"
args = ["-y", "@axiolex/mcp-gateway", "--endpoint", "http://localhost:9700/mcp"]For a remote Axiolex server, replace http://localhost:9700/mcp with your endpoint URL.
Options
| Option | Env var | Default | Description |
|---|---|---|---|
| --endpoint, -e | AXIOLEX_URL | http://localhost:9700/mcp | Axiolex MCP HTTP endpoint |
| --help, -h | | | Show help |
How it works
MCP Client (Claude, Cursor, Codex)
└── spawns: npx @axiolex/mcp-gateway --endpoint http://localhost:9700/mcp
├── stdio server (stdin/stdout) ← client sends JSON-RPC here
├── HTTP client (fetch) → forwards to localhost:9700/mcp
└── returns response via stdout ← client receives resultThe proxy connects to the Axiolex server on startup (MCP initialize handshake), then forwards tools/list, tools/call, prompts/list, and prompts/get requests. All retrieval, ranking, and execution happens server-side — the proxy is just a pipe.
Capabilities
The proxy advertises the following MCP capabilities to the client:
- tools (
listChanged: false) —tools/listandtools/callproxied to upstream - prompts (
listChanged: false) —prompts/listandprompts/getproxied to upstream
See the Axiolex prompts catalog for available prompts.
Requirements
- Node.js 18+ (pre-installed on most developer machines)
- An Axiolex server running and reachable at the configured endpoint
License
MIT
