OrcaRouter

io.github.Continuum-AI-CorpPublished by GitHub account Continuum-AI-Corpv1.1.5Updated Oct 24, 2026

Browse 160+ LLM models and live pricing — no API key needed for catalog. Add key to route chat.

The publisher's own server: 370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

VerifiedSTDIODesktop onlyData & AnalyticsAI & ML

Overview

AI-generated overview

OrcaRouter's MCP server lets an assistant browse a catalog of 160+ LLM models with pricing and run chat completions through the OrcaRouter gateway.

What you can do
List providers and models, filtered by provider, capability or minimum context window, with pricing and capabilities visible without an API key. Inspect a detailed model card for one model: pricing, context, latency and supported endpoints. Run chat completions through any served model, optionally with an auto-routing strategy or a fallback chain of a primary plus up to four fallbacks.
When to use it
Useful when you want to compare LLM models and pricing from inside an MCP client, or route chat requests through the OrcaRouter gateway with fallbacks instead of calling a single provider directly.
Requirements
Runs locally over stdio via the npm package, requiring Node.js 18 or later. The ORCAROUTER_API_KEY environment variable is needed only for chat completions; catalog tools work without it. Optional ORCAROUTER_BASE_URL and ORCAROUTER_REQUEST_TIMEOUT variables adjust the gateway endpoint and per-request timeout.
Before you install
Chat completions send prompts to the OrcaRouter gateway and its upstream model providers, and may incur usage costs on your account. The API key is read from ORCAROUTER_API_KEY; keep it out of shared config files. Desktop clients only.

Installation

In SourceWeft

  1. Open OrcaRouter in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[OrcaRouter]

OrcaRouter MCP Server

Official MCP server for the OrcaRouter LLM gateway.

[Discord] [X] [npm version] [CI] [Smithery]

English | 日本語 | 中文 | 한국어 | Deutsch | Français | Español | Italiano | Русский | Português | Tiếng Việt | हिन्दी


Browse OrcaRouter's model catalog and run chat completions from inside any Model Context Protocol client — Claude Desktop, Claude Code, Cursor, Windsurf, Zed, or anything else that speaks the protocol.

Catalog browsing works without an API key — compare pricing and capabilities before signing up.

What you can do

  • 🗺️ Discover providers and models without an API key
  • 💬 Run chat completions through any served model
  • 🧠 Auto-route requests through your workspace's orcarouter/auto router (cost / quality / balanced / LinUCB / gated-adaptive strategies)
  • 🔁 Configure fallback chains (primary + up to 4 fallbacks) for resilience
  • 📊 Filter models server-side by provider, capability, or minimum context window
  • 🎯 Inspect detailed model cards: pricing, context, latency, supported endpoints
  • 🔌 Works with Claude Desktop, Claude Code, Cursor, Windsurf, Zed, and any MCP client

Examples

Try saying things like:

  • "List all providers on OrcaRouter"
  • "Show me all Anthropic models with their pricing"
  • "Get details about minimax/minimax-m2.7"
  • "Chat with orcarouter/auto and explain quantum computing"

Quick Start

Claude Code (CLI one-liner)

bash
claude mcp add orcarouter -s user \  -e ORCAROUTER_API_KEY=sk-orca-your-key \  -- npx -y @orcarouter/mcp

Other clients (config-file path)

  1. Copy the example config for your MCP client into the client's config file:

    ClientExampleAction
    Claude Desktopclaude-desktop.jsonReplace
    Claude Codeclaude-code.jsonMerge
    Cursorcursor.jsonReplace
    Windsurfwindsurf.jsonReplace

    See examples/README.md for the config-file paths and notes on Zed and other clients.

  2. Replace sk-or-... in the copied file with your OrcaRouter API key.

  3. Restart your MCP client.

The root .mcp.json is the same config in the Open Plugins standard location, so registry/discovery tools that scan for it (e.g. cursor.directory) can pick this server up automatically.

Requires Node.js 18 or later. The ORCAROUTER_API_KEY env var is only required for orcarouter_chat; catalog tools work without it.

Tools

  • orcarouter_chat — run a chat completion (with optional fallback chain)
  • orcarouter_models_list — browse the catalog (pricing, context, capabilities)
  • orcarouter_model_card — detailed info for one model
  • orcarouter_providers_list — list providers with model counts

Full input schemas are exposed at runtime via the MCP tools/list method — your MCP client (Claude Desktop, Cursor, etc.) reads them automatically.

Configuration

NameRequiredDescription
ORCAROUTER_API_KEYoptionalOrcaRouter API key. Required only for orcarouter_chat.
ORCAROUTER_BASE_URLoptionalAPI base URL. Defaults to https://api.orcarouter.ai.
ORCAROUTER_REQUEST_TIMEOUToptionalPer-request HTTP timeout in seconds. Defaults to 300.

Security

API keys are read from environment variables, never logged, and only sent to the OrcaRouter API. See SECURITY.md for the vulnerability disclosure policy.

Development

sh
# bun (preferred)bun installbun run testbun run typecheckbun run build
# or with npmnpm installnpm testnpm run typechecknpm run build

The build produces an ESM bundle at dist/index.js with a #!/usr/bin/env node shebang, runnable as the orcarouter-mcp binary.

Contributing

See CONTRIBUTING.md. For newcomer-friendly tasks, browse the good first issue label.

License

MIT

Source: README.md at commit 02084c3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.5LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Router integrations