npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@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.

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-gateway

Client 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 result

The 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/list and tools/call proxied to upstream
  • prompts (listChanged: false) — prompts/list and prompts/get proxied 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