unorouter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UNOROUTER_API_KEY | Yes | API key for UnoRouter. Create one at https://unorouter.com/token | |
| UNOROUTER_BASE_URL | No | Base URL for the UnoRouter API. Defaults to https://api.unorouter.com | https://api.unorouter.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_modelsA | Search the live UnoRouter model catalog (200+ models behind one OpenAI-compatible key). Models ending in :free cost nothing. Returns matching model IDs usable with the chat tool or any OpenAI-compatible client pointed at https://api.unorouter.com/v1. |
| chatA | Send a single prompt to any UnoRouter model and return the reply. Use search_models to find model IDs; :free models cost nothing (light per-model rate limit, rotate models if you hit 429). |
| get_pricingA | Look up per-token pricing for UnoRouter models from the public pricing endpoint. Prices are USD list prices per 1M tokens before per-group discounts (the account dashboard shows the exact effective rate). :free models are always 0. |
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 3 tools
Each tool targets a distinct concern: model discovery, pricing lookup, and chat completion. There is no overlap or ambiguity between them.
Two tools follow the verb_noun pattern (search_models, get_pricing), while 'chat' is a bare verb. This is a minor deviation but the set remains readable and predictable.
Three tools is appropriately scoped for a model-routing/chat API. Each tool has a clear purpose and none feel redundant or missing.
The surface covers the essential workflows: discover models, check pricing, and send chats. Minor gaps like streaming or detailed model metadata exist but are not critical for the core use case.