OpenRouter MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENROUTER_MODEL | No | Model to use | openai/gpt-4o |
| OPENROUTER_API_KEY | Yes | Your OpenRouter API key | |
| OPENROUTER_TIMEOUT | No | Request timeout (seconds) | 90 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| consult_openrouterB | Consult OpenRouter API in non-interactive mode with structured output. Processes prompt and returns formatted response. Supports text, JSON, and code extraction formats. Args: query: The prompt to send to OpenRouter directory: Working directory (required) - for context only format: Output format - "text", "json", or "code" (default: "json") timeout: Optional timeout in seconds (overrides env var, recommended: 60-120) Returns: Formatted response based on format parameter |
| consult_openrouter_with_stdinA | Consult OpenRouter with stdin content piped to prompt. Similar to 'echo "content" | open-bridge "prompt"' - combines stdin with prompt. Perfect for CI/CD workflows where you pipe file contents to the AI. Args: stdin_content: Content to pipe as stdin (e.g., file contents, diff, logs) prompt: The prompt to process the stdin content directory: Working directory (required) format: Output format - "text", "json", or "code" (default: "json") timeout: Optional timeout in seconds (overrides env var, recommended: 60-120) Returns: Formatted response based on format parameter |
| consult_openrouter_batchA | Consult multiple OpenRouter queries in batch - perfect for CI/CD automation. Processes multiple prompts concurrently and returns consolidated JSON output. Each query can have individual timeout and format preferences. Args: queries: List of query dictionaries with keys: 'query' (required), 'timeout' (optional) directory: Working directory (required) format: Output format - currently only "json" supported for batch Returns: JSON array with all results |
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 has a clearly distinct purpose: single query, batch processing, and stdin-piped input. Despite all consulting OpenRouter, the different use cases prevent confusion.
All tools follow a consistent 'consult_openrouter_<modifier>' pattern, making it easy to predict functionality from the name.
Three tools cover the essential interaction modes for the OpenRouter API bridge, neither over nor under-scoped for its purpose.
The set covers the primary consult operation in three modes, which is sufficient for the bridge's core purpose. Minor missing features like model listing are not essential for 'consult' functionality.