F
licenseNot graded
qualityD
maintenanceLocal MCP server that exposes fixed tools for GPT, Claude, and Gemini while routing to any OpenAI-compatible chat completions backend with independent configuration per target.
1
-
dxt-openrouter-router
by sphilius
Related Servers
Alternatives to dxt-openrouter-router
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables AI coding assistants to interact with OpenRouter API for direct queries, file analysis, and batch processing.3MIT
- FlicenseBqualityBmaintenanceAn intelligent, agentic MCP server gateway to OpenRouter's 200+ AI models. It provides budget controls, security features, semantic memory, and code search capabilities.24-
- AlicenseNot gradedqualityDmaintenanceMCP server that routes AI chat requests to the best available provider (Anthropic, OpenAI, Groq, etc.) with automatic fallback, budget caps, and model-tier routing.MIT
- AlicenseNot gradedqualityDmaintenanceA simple server that acts as a Master Control Program (MCP) for unified interaction with OpenAI and Anthropic (Claude) AI models through a single API endpoint.33 npmMIT
- AlicenseAqualityAmaintenanceA Python MCP server that lets MCP hosts call OpenRouter models for chat, image generation, embeddings, and model search via FastMCP with .env support and retry handling.598 PyPI1MIT
TDQS
A3.8/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of ambiguity or overlap with other tools. The purpose of routeLLM is clearly defined and distinct.
Naming Consistency3/5
With only a single tool, there is no pattern to evaluate for consistency. The name routeLLM uses a camelCase convention mixing a verb and a domain noun, which is readable though generic.
Tool Count2/5
A single tool feels thin for a server named 'openrouter-router.' The router domain likely requires at least companion operations (e.g., send, list presets, get budget) to be practically useful on its own, so one tool is under-scoped.
Completeness2/5
The tool only builds a request body and explicitly does not send the request. For routing purposes, there is a notable dead end—no send capability, no way to list/manage presets, and no health or configuration operations. The surface is significantly incomplete for the stated routing purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues