OpenRouter MCP Server
Related Servers
Alternatives to OpenRouter MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceProvides access to OpenRouter.ai's diverse model ecosystem for text chat and image analysis capabilities, with support for multimodal conversations and automatic image optimization.712 npm-
- AlicenseNot gradedqualityDmaintenanceProvides seamless access to 200+ AI models through OpenRouter's unified API, featuring multi-model collaboration, vision support, intelligent benchmarking, and collective intelligence capabilities for enhanced decision-making.133 npm9MIT
- AlicenseAqualityDmaintenanceProvides integration with OpenRouter.ai, allowing access to various AI models through a unified interface.4211 npm63Apache 2.0
- AlicenseBqualityAmaintenanceProvides chat and image analysis capabilities through OpenRouter.ai's diverse model ecosystem, enabling both text conversations and powerful multimodal image processing with various AI models.11787 npm88Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables chat and image analysis through OpenRouter.ai models. Supports text chat, image generation, and analysis with multiple images and custom questions.787 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants like Claude or ChatGPT to query OpenRouter's 300+ models for pricing, context length, capabilities, and rankings through tools such as model-card, compare-models, cheapest-for, cost-estimator, and usage-rankings, using a public, key-less API with 6-hour caching.94 npm1MIT
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.