OpenRouter MCP Server
Related Servers
Alternatives to OpenRouter MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server providing a model-agnostic subagent tool backed by OpenRouter, supporting multi-model Fusion and orchestration patterns.31MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that functions as an intelligent gateway for multiple LLM backends including OpenAI, Claude, and Ollama. It supports automatic provider fallback, streaming responses via Server-Sent Events, and real-time monitoring for robust AI integration.MIT
- AlicenseCqualityBmaintenanceAn MCP server offering hybrid memory recall and continuity tools for AI agents. It also provides a governance gateway that pre-approves risky shell/file/git actions before execution.19Apache 2.0
- AlicenseAqualityDmaintenanceA lightweight MCP server that enables AI coding assistants to interact with OpenRouter API for direct queries, file analysis, and batch processing.3MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that enables agents to dynamically switch between multiple AI models (OpenAI, Anthropic, Google, etc.) with unified protocol-driven configuration and capability discovery.Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
TDQS
Scored across 24 tools
Several tools have overlapping chat generation purposes (chat_completion, chat_with_preset, chat_ensemble, chat_routed) but descriptions distinguish them by mode. Code search tools (search_symbols vs semantic_code_search) and indexing tools (index_project vs reindex_project) are also similar, though their intents are clear enough.
Most tools follow a verb_noun snake_case pattern (list_models, get_balance, pin_context). Minor deviations like chat_with_preset (preposition) and chat_routed (past participle) are understandable but break the strict pattern.
At 24 tools, the server is on the heavy side. It bundles unrelated domains (OpenRouter chat, code indexing, memory, error correlation) into one surface, which feels over-scoped for a single MCP server.
Core OpenRouter operations (chat, models, budget, usage) are well covered. The supplementary features (indexing, memory) have CRUD-style operations, though delete for indexing and some model detail endpoints are missing. Overall, most workflows can be completed.