Skip to main content
Glama
itstanner5216

Multi MCP

by itstanner5216
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Multi MCP

No user-submitted related servers found.

    Related Servers

    • Multi-MCP Proxy

      kfirtoledo
      A
      license
      Not graded
      quality
      D
      maintenance
      A flexible MCP proxy server that connects to and routes between multiple backend MCP servers over STDIO or SSE, enabling dynamic management and namespacing of tools.
      110
      MIT

    • MCP Manager

      daniel3303
      A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.
      18
      MIT

    • drunk-mcp-proxy

      baoduy
      A
      license
      Not graded
      quality
      C
      maintenance
      A dynamic proxy server that enables users to manage and access multiple MCP backend servers through a single, unified interface. It supports both static and runtime server configuration with persistent storage and works with HTTP and SSE transports.
      MIT

    • proxy-mcp

      Rixmerz
      F
      license
      A
      quality
      D
      maintenance
      Universal MCP proxy server that discovers, searches, and executes tools across all configured MCP servers from a single entry point.
      7
      -

    • MCPDog

      QiuZwan
      A
      license
      Not graded
      quality
      B
      maintenance
      Aggregates multiple MCP sub-servers into a single unified entry point, supporting stdio and Streamable HTTP protocols, with a web-based management interface for configuration, routing, and tool management.
      41 npm
      MIT
    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

    B3/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: two are for mathematical operations (addition and multiplication) and one is for weather retrieval. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.

    Naming Consistency3/5

    The naming is mixed: 'calculator__add' and 'calculator__multiply' follow a consistent 'domain__verb_noun' pattern, but 'weather__get_weather' uses a different structure with a redundant 'weather' term. This inconsistency reduces predictability, though the names remain readable.

    Tool Count2/5

    With only three tools, the server feels thin and under-scoped for a 'Multi MCP' name that suggests broader functionality. The tools cover two unrelated domains (calculator and weather), lacking depth in either area, which may limit agent effectiveness.

    Completeness2/5

    The tool surface is severely incomplete. For the calculator domain, basic operations like subtraction and division are missing, and for weather, there are no tools for forecasts or historical data. This creates significant gaps that will likely cause agent failures in handling related tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources