Openrouter logo

Openrouter

Inspect, filter, and compare OpenRouter models by pricing, context size, modality, and supported features.

Install Openrouter

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "openrouter": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-openrouter"
      ],
      "env": {
        "PIPEWORX_API_KEY": "YOUR_VALUE_HERE",
        "PIPEWORX_META_TOOLS": "YOUR_VALUE_HERE",
        "NODE_USE_ENV_PROXY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Openrouter MCP server exposes OpenRouter’s model catalog through tools for listing, inspecting, and comparing models. It reports normalized pricing per million tokens alongside context windows, modalities, supported parameters, and related model metadata. Connect through the hosted MCP endpoint, use the local npm stdio bridge, or call tools over HTTP when an MCP client is not available. Reach for it when an agent needs current model-selection data without an OpenRouter API key.

Use cases

  • Find free OpenRouter models with a required context window
  • Compare model pricing before selecting an LLM
  • Inspect modality and supported parameters for a model
  • Query OpenRouter catalog metadata from an MCP client

Key features

  • Filterable OpenRouter model catalog
  • Normalized pricing per million tokens
  • Detailed model metadata lookup
  • Side-by-side comparison for 2-5 models
  • Hosted MCP, local stdio, and HTTP access

Tools3

What Openrouter lets your agent do. Expand a tool for its parameters.

Verified live~451 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

7/7 checks healthy over the last 54d

What it can do

From the 3 tools this server returned when we ran it.

Handles credentials · 2Makes network requests · 1Read-only tools · 3
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age132 days
Maintainers1

Observed 2026-10-21 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · @pipeworx/mcp-openrouter (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.4kPackage downloads in the last 30 days.
Last commit3d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Openrouter works

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:

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

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

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

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Openrouter

Openrouter is an MCP server that connects AI agents to the OpenRouter model catalog through Pipeworx. Its main tools list models with filters, retrieve detailed metadata for one model, and compare two to five models by pricing, context window, and modality. The catalog tools do not require an OpenRouter API key.

Install it by adding the hosted MCP URL to your client or running the npm stdio bridge with npx. Use https://gateway.pipeworx.io/openrouter/mcp for the hosted connection, or configure @pipeworx/mcp-openrouter with the command npx and the -y package argument.

Yes, Openrouter works with Cursor through the hosted MCP endpoint. Add https://gateway.pipeworx.io/openrouter/mcp as an MCP server URL in Cursor, then use the list_models, get_model, and compare_models tools.

No, an API key is not required for anonymous use. Anonymous calls are limited to 50 per day; adding a Pipeworx API key with PIPEWORX_API_KEY raises the allowance to 200 calls per day through a free account.

Yes, you can call its tools over HTTP without an MCP client. For example, send a POST request to https://gateway.pipeworx.io/v1/tools/openrouter_list_models with a JSON body such as {"search":"claude","limit":10}.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewOpenrouter AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/openrouter?style=directory)](https://allmcps.com/mcp/openrouter)
HTML Embed
<a href="https://allmcps.com/mcp/openrouter"><img src="https://allmcps.com/api/badge/openrouter?style=directory" alt="Openrouter on AllMCPs" /></a>