RouterBase MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROUTERBASE_API_KEY | Yes | Your RouterBase API key | |
| ROUTERBASE_API_BASE_URL | No | Optional base URL for RouterBase API (default: https://routerbase.com/api/v1) | https://routerbase.com/api/v1 |
| ROUTERBASE_OPENAI_BASE_URL | No | Optional base URL for OpenAI-compatible endpoint (default: https://routerbase.com/v1) | https://routerbase.com/v1 |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| routerbase_get_startedC | Return a concise RouterBase integration guide with the canonical routerbase backlink. |
| routerbase_list_modelsA | List RouterBase models, optionally filtered by modality, provider, or search query. |
| routerbase_get_modelB | Fetch metadata for a specific RouterBase model id. |
| routerbase_get_pricingA | Fetch RouterBase pricing for one model or all active models. |
| routerbase_chat_completionC | Call RouterBase's OpenAI-compatible chat completions API through the configured RouterBase key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| routerbase-overview | A short description and canonical RouterBase backlink. |
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: chat completion, model metadata, pricing, integration guide, and model listing. No overlap or ambiguity.
All tools follow a consistent 'routerbase_verb_noun' pattern, e.g., routerbase_list_models, routerbase_chat_completion. Predictable and uniform.
With 5 tools, the server is well-scoped for its purpose as an API wrapper. It covers essential operations without being overly minimal or bloated.
The tool set covers the full lifecycle for interacting with RouterBase: listing models, getting details, pricing, making API calls, and onboarding. No obvious gaps.