Skip to main content
Glama
groxaxo

mcp-llm-router

by groxaxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-llm-router

No user-submitted related servers found.

    Related Servers

    • llm-gateway-mcp

      felmarv
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hostable MCP server that routes prompts to multiple LLM providers using declarative policies, with multi-role orchestration for independence and verification.
      MIT

    • llm-localfirst

      shaxzodbek-uzb
      A
      license
      Not graded
      quality
      B
      maintenance
      A local-first LLM routing MCP server that keeps sensitive data on your own models, with fail-closed privacy and manager-worker delegation, exposing route and complete tools to any MCP client.
      MIT

    • Multi-Provider LLM MCP Server

      itachiuchihadev
      F
      license
      A
      quality
      B
      maintenance
      Unified MCP server for querying multiple LLM providers (Gemini, OpenAI, Anthropic, etc.) with advanced routing, cost optimization, and fallback resilience.
      2
      6 npm
      -

    • MCP Context Hub

      DiegoNogueiraDev
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A local MCP server for RAG memory, semantic search, and context optimization using Ollama and SQLite. It serves as a central hub that manages document embeddings, text compression, and proxies calls to other sub-MCP servers.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.5/5.0

    Scored across 28 tools

    Disambiguation3/5

    Some tool clusters overlap in purpose: router_chat vs agent_llm_request both make LLM calls, list_mcp_servers vs list_mcp_tools are easy to confuse, and the judge_* family shares a similar naming pattern despite targeting different phases. Most tools are distinct, but the boundaries between some are unclear without reading the full descriptions.

    Naming Consistency4/5

    The vast majority of tools follow a verb_noun snake_case pattern (start_session, set_coding_task, judge_code_change). Exceptions like the memory_* noun-prefixed family, router_chat, and agent_llm_request deviate, but the overall convention is still fairly uniform.

    Tool Count2/5

    At 28 tools, this server exceeds the 25-tool threshold and spans many subdomains (memory, sessions, MCP, coding workflow). Each tool appears purposeful, but the large surface area creates context and selection overhead for an agent.

    Completeness4/5

    The server covers the full coding task lifecycle (plan, code review, testing, completion) and provides robust memory, session, and MCP management. Minor gaps like no session teardown or MCP disconnect exist, but agents can work around them.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources