orcarouter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORCAROUTER_API_KEY | No | OrcaRouter API key. Required only for orcarouter_chat. | |
| ORCAROUTER_BASE_URL | No | API base URL. Defaults to https://api.orcarouter.ai. | https://api.orcarouter.ai |
| ORCAROUTER_REQUEST_TIMEOUT | No | Per-request HTTP timeout in seconds. Defaults to 300. | 300 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| orcarouter_chatA | Send a single-turn chat request to OrcaRouter and return the assistant's response text. Default model is the workspace's auto-router. Use |
| orcarouter_models_listA | List LLM models in the OrcaRouter catalog. Each entry includes id, name, description, owned_by, context_length, supported_endpoint_types, and pricing (both per-token and per-million tokens). Filter by |
| orcarouter_model_cardA | Get detailed information about a single model — display name, long description, pricing (per-call and per-million tokens), context window, max output, modalities (input/output), supported endpoints, latency percentiles (p50/p95), and release date. Use this when you already know the model id and want full details; for browsing or filtering across many models use orcarouter_models_list instead. Returns isError:true with a clear hint when the id is not found. Read-only, no API key required. |
| orcarouter_providers_listA | List all model providers on OrcaRouter with their |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: chat, model card, model listing, and provider listing. No overlap or ambiguity.
All tools follow the consistent pattern 'orcarouter_<noun>', using snake_case throughout. The naming is predictable and uniform.
With 4 tools, the server is well-scoped for its purpose—covering chat and model catalog exploration without unnecessary bloat.
Core operations (chat, model info, model listing, provider listing) are present. Minor gap: no health/status tool, but functionality is largely complete.