openrouter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key | |
| OPENROUTER_SYSTEM_PROMPT | No | Default system prompt for all requests | |
| OPENROUTER_ALLOWED_MODELS | Yes | Comma-separated list of allowed model IDs |
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 |
|---|---|
| ask_modelA | Consult another AI model for help with coding tasks. Use this to get a second opinion, ask for explanations, or request assistance with complex problems. |
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 1 tool
With only one tool, there is no risk of confusion between tools. The single tool is clearly distinct by default.
The tool name 'ask_model' follows a clear verb_noun convention, which is appropriate and consistent though there is only one tool.
A single tool feels thin for a server named 'openrouter-mcp', which implies broader model access capabilities. However, it may be scoped to just querying models, making it borderline acceptable.
The tool covers the core action of asking a model, but lacks supporting tools like listing available models or retrieving model metadata, which are notable gaps for a server focused on model access.