qiaomu-llm-mcp
Related Servers
Alternatives to qiaomu-llm-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceUnified AI gateway that aggregates MCP tools from multiple servers and routes LLM requests with provider combos and fallback, all managed through a web UI.1MIT
- FlicenseNot gradedqualityDmaintenanceUnified local MCP AI Gateway that routes across Groq, OpenRouter, Mistral, and local Ollama providers, with OpenAI-compatible APIs, MCP tools, fallback/racing router, monitoring, and web dashboard.-
- FlicenseNot gradedqualityAmaintenanceA local AI gateway that connects multiple AI providers (ChatGPT, Claude, Gemini, Perplexity) to your development environment via MCP tools, enabling coding, search, analysis, and more without API keys.17 npm1,171-
- FlicenseCqualityDmaintenanceAn MCP server that routes LLM requests across multiple providers and orchestrates other MCP servers, with a focus on local privacy for embeddings and memory.283-
- 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

Bifrost MCP Gatewayofficial
AlicenseNot gradedqualityBmaintenanceOpen-source MCP and LLM gateway that aggregates MCP tools behind a unified endpoint with governance, observability, and explicit execution controls.8,078Apache 2.0
TDQS
Scored across 13 tools
Each tool has a clear, distinct purpose. For example, qllm_chat handles single provider calls, qllm_compare compares multiple providers, and qllm_heavy_discuss facilitates multi-perspective discussions. The Claude Code tools are specialized and separate from the general chat and management tools.
All tools follow a consistent 'qllm_' prefix and snake_case naming convention. They use a verb_noun pattern (e.g., list_models, show_provider, claude_code_run) that makes their function predictable and easy to parse.
With 13 tools, the set is well-scoped. It covers chat, comparison, heavy discussion, pipelines, routing, provider management, and Claude Code integration without being excessive or sparse. Each tool addresses a specific need within the domain.
The tool set comprehensively covers the core operations of a local LLM registry: listing providers and models, calling models in various configurations (single, compare, heavy discuss, pipeline), routing, and Claude Code integration. No obvious gaps are present for the stated purpose.