# Openrouter [Health: Active]

**Category:** 🗣️ Conversational AI  
**Repository:** https://github.com/pipeworx-io/mcp-openrouter  
**GitHub Stars:** 0  
**npm Downloads (last month):** 3126  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/openrouter

## Description
OpenRouter Models MCP.

## Tools
Capabilities this server exposes over MCP:

- **openrouter_list_models** — List LLMs from the OpenRouter catalog (~340 models across all major providers) with normalized $/1M-token pricing, context windows, and modality. Filter by search, free-only, minimum context, or modality (e.g. "image" for vision models). Sorted cheapest-first by completion price. Keyless.
- **openrouter_get_model** — Get full details for one OpenRouter model by id, normalized $/1M pricing (prompt, completion, plus per-request/image/web-search costs), context window, modality, supported parameters, tokenizer, knowledge cutoff. e.g. id "anthropic/claude-sonnet-4.5". Keyless.
- **openrouter_compare_models** — Side-by-side comparison of pricing ($/1M tokens), context window, and modality for 2-5 OpenRouter models. Answers "is claude-sonnet-4.5 cheaper than gpt-4o". Keyless.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "openrouter": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-openrouter"],
    "env": {
      "PIPEWORX_API_KEY": "",
      "PIPEWORX_META_TOOLS": "",
      "NODE_USE_ENV_PROXY": ""
    }
  }
}
```

**Requires environment variables:** `PIPEWORX_API_KEY`, `PIPEWORX_META_TOOLS`, `NODE_USE_ENV_PROXY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Openrouter does

Openrouter MCP server gives MCP clients access to model metadata from the OpenRouter catalog. Its primary use is model discovery and selection rather than sending prompts to models. The catalog covers roughly 340 models from major providers and presents comparable fields such as prompt and completion pricing per million tokens, context limits, and modality.

The server is an independent, unofficial Pipeworx integration. It connects to the Pipeworx gateway, which provides the OpenRouter-specific tools and shared gateway capabilities.

## How it works

A hosted streamable MCP endpoint is available at `https://gateway.pipeworx.io/openrouter/mcp`. An MCP client can connect directly to that URL and discover the OpenRouter tools. The same gateway also exposes a full endpoint at `https://gateway.pipeworx.io/mcp`; the OpenRouter endpoint lists this pack’s tools directly, while the full endpoint lists tools from every pack directly.

The gateway may also expose shared Pipeworx tools, including `ask_pipeworx`, `discover_tools`, `search_within`, and memory-related tools. The exact tool scope is reported by the connection’s `initialize` response. `ask_pipeworx` can route a natural-language question across the wider gateway catalog, including from the OpenRouter pack endpoint.

For local MCP setups, `@pipeworx/mcp-openrouter` runs as a Node-based stdio bridge. The client starts it with `npx`, and the bridge forwards requests to the hosted gateway, so it requires network access and has no offline mode. HTTP clients can call the gateway’s tool routes directly, such as `POST /v1/tools/openrouter_list_models`.

## Setup and configuration

Add the hosted endpoint to an MCP client with a server entry like this:

```json
{
  "mcpServers": {
    "openrouter": {
      "url": "https://gateway.pipeworx.io/openrouter/mcp"
    }
  }
}
```

For a local stdio connection, configure the npm package instead:

```json
{
  "mcpServers": {
    "openrouter": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-openrouter"]
    }
  }
}
```

Anonymous use is available with a limit of 50 calls per day. A free Pipeworx account increases that allowance to 200 calls per day. Set `PIPEWORX_API_KEY` in the client’s environment to authenticate with a Pipeworx key. Set `PIPEWORX_META_TOOLS=1` if the local bridge should also list the shared gateway tools.

When running behind an HTTPS proxy, newer Node versions can use proxy environment settings when `NODE_USE_ENV_PROXY=1` is enabled.

## Tools and capabilities

- `list_models` searches the OpenRouter catalog and can filter by text, free availability, minimum context length, or modality. Results are ordered by completion price, from lowest to highest.
- `get_model` returns detailed metadata for one model ID, including prompt and completion prices, per-request, image, and web-search charges, context size, modality, supported parameters, tokenizer, and knowledge cutoff.
- `compare_models` compares two to five model IDs by pricing, context window, and modality.

The catalog and tool results are keyless at the OpenRouter level. Example model IDs use the provider/model format, such as `anthropic/claude-sonnet-4.5`.

## Limitations and notes

The local bridge depends on the hosted Pipeworx gateway and cannot operate offline. Anonymous calls are capped at 50 per day, while authenticated free accounts receive 200 calls per day. Pack endpoints currently include shared gateway metadata tools in addition to the pack’s own tools; use the `initialize` response as the authoritative scope for a connection. This integration is unofficial and is not affiliated with, endorsed by, or published by OpenRouter.

_Full upstream README: https://allmcps.com/mcp/openrouter/readme_

