Summary
The OpenRouter MCP server helps you select the right AI model for your use case. Get recommendations based on vision support, audio support, tool calling, budget tier, and context length requirements. Search the model catalog with fuzzy matching and get detailed pricing and capability information.Authentication
No authentication required. This server uses publicly available data from OpenRouter’s API.Use Cases
Finding a Budget Model with Vision Support
User: “I need a cheap model that can analyze images” Tool Calls:recommend-modelwithrequire_vision: true,preferred_tier: "Budget"→ Returns budget-friendly vision models
Choosing a Model for Code Review
User: “What’s the best model for reviewing code? I need function calling.” Tool Calls:recommend-modelwithuse_case: "code review",require_tools: true→ Returns models optimized for code tasks with tool support
Searching for a Specific Model
User: “What’s the pricing for GPT-4o?” Tool Calls:search-modelswith query “gpt-4o” → Finds matching modelsget-model-detailswith model_id “openai/gpt-4o” → Full pricing and capability details
Available Tools
recommend-model
Get AI model recommendations based on your requirements.
Returns:
- Top matching models with detailed reasoning
- Comparison table of pricing, context length, and capabilities
- Best use case for each recommended model
Pricing Tiers:
- Budget: < $1 per 1M input tokens (great for high volume)
- Standard: $1-5 per 1M input tokens (balanced performance)
- Premium: > $5 per 1M input tokens (highest quality)
list-models
List all available AI models from OpenRouter, optionally filtered by capabilities.
Returns: Models organized by pricing tier with tables showing name, price, context length, and supported capabilities.
Example:
Empty Tiers: Tiers with no matching models are automatically removed from the output.
get-model-details
Get detailed information about a specific model by its ID.
Returns:
- Provider and tier information
- Modality (text, text+vision, text+audio)
- Pricing per 1M tokens with example cost calculation
- Capabilities (tools, vision, audio)
- Context window with approximate word and page counts
- Usage example
Model Not Found: If the model_id doesn’t exist, the tool returns an error with suggestions for similar models.
search-models
Search for AI models using fuzzy matching across names, IDs, providers, and descriptions.
Returns: Matching models in table format with provider, tier, pricing, context length, and capabilities.
Example:
- Model name (e.g., “claude”, “gpt”, “gemini”)
- Model ID (e.g., “anthropic/claude-sonnet-4”)
- Provider name (e.g., “openai”, “anthropic”, “google”)
- Model description
Typo Tolerance: The fuzzy search handles typos and partial matches. Try “claud” or “gpt4o” and you’ll still find the right models.
Common Workflows
Choosing a Model for a New Project
1
Define Requirements
Determine if you need vision, audio, tools, specific context length, or budget constraints
2
Get Recommendations
Use
recommend-model with your requirements and use case3
Review Details
Use
get-model-details for top recommendations to compare pricing and features4
Select Model
Choose based on the balance of capabilities, performance, and cost
Finding Models Within Budget
1
Set Budget Constraint
Use
list-models with tier: "Budget" or set max_price_per_million2
Filter by Capabilities
Add
require_vision, require_tools, or require_audio as needed3
Compare Options
Review the filtered list and use
get-model-details for specific modelsExploring Model Capabilities
1
Search by Name
Use
search-models with the model name or provider2
Get Full Details
Use
get-model-details with the exact model_id from search results3
Compare Alternatives
Use
recommend-model with similar requirements to find alternativesModel Capability Reference
Tool/Function Calling
Models with tool support can call external functions to fetch data or perform actions. Essential for:- Agentic workflows
- Real-time data access
- Integration with external APIs
Vision/Image Input
Models with vision can analyze images, screenshots, charts, and diagrams. Useful for:- Document analysis
- Image-based Q&A
- UI/UX feedback
- Visual content moderation
Audio Input
Models with audio can process spoken audio. Useful for:- Transcription
- Voice assistants
- Audio content analysis
Context Length
Determines how much text the model can process at once:- 32K tokens (~24K words, ~96 pages): Suitable for short documents
- 128K tokens (~96K words, ~384 pages): Good for medium documents and conversations
- 200K tokens (~150K words, ~600 pages): Great for long documents
- 1M+ tokens (~750K words, ~3000 pages): Handles entire codebases or books
Tips & Best Practices
- Start with use case in
recommend-modelfor better context-aware recommendations - Budget tier doesn’t mean low quality - models like Gemini 2.0 Flash offer excellent performance at budget pricing
- Context length matters - if you’re processing large documents, filter by
min_context_length - Check pricing carefully - output tokens are typically more expensive than input tokens
- Tool support is crucial for Agentic Loops - enable
require_tools: truewhen building autonomous workflows - Use fuzzy search when you’re not sure of the exact model name
API Reference
View the complete API specification for OpenRouter MCP server endpoints