OpenRouter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key (required) | |
| OPENROUTER_APP_NAME | No | Application name for API headers | |
| OPENROUTER_BASE_URL | No | API base URL | https://openrouter.ai/api/v1 |
| OPENROUTER_SITE_URL | No | Your site URL for API attribution |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_modelsB | Get list of available OpenRouter models |
| chat_with_modelB | Send a message to a specific OpenRouter model |
| compare_modelsC | Compare responses from multiple models |
| get_model_infoC | Get detailed information about a specific model |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Available Models | List of all available OpenRouter models with pricing |
| Model Pricing | Current pricing information for all models |
| Usage Statistics | Your OpenRouter usage statistics |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: chat_with_model is for sending messages, compare_models is for comparing multiple models, get_model_info is for retrieving details about a specific model, and list_models is for listing available models. There is no overlap or ambiguity between these functions.
All tool names follow a consistent verb_noun pattern (e.g., chat_with_model, compare_models, get_model_info, list_models). The naming is uniform and predictable throughout the set.
With 4 tools, the server is well-scoped for interacting with OpenRouter models. Each tool serves a distinct and necessary function, and the count is appropriate for the domain without being too sparse or bloated.
The tool set covers core operations for model interaction: listing, getting info, chatting, and comparing. A minor gap is the lack of tools for managing API keys or handling billing, but these are not essential for the primary use case.