Skip to main content
Glama

Related Servers

Alternatives to proxy-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A standalone MCP gateway/proxy server that lets any MCP-compatible client search and call tools across multiple downstream MCP servers through a single mcp proxy tool.
      22 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.
      9
      377
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A flexible proxy server that aggregates multiple backend MCP servers into a single interface using STDIO or SSE transports. It supports dynamic server management via an HTTP API and utilizes namespacing to prevent tool conflicts across connected services.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates multiple backend MCP servers into a single unified interface with optional web management UI for tool control and configuration.
      43 npm
      194
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A proxy MCP server that aggregates tools from multiple MCP servers and forwards calls to the appropriate server, used with the Metatool App for GUI tool management.
      5
      Apache 2.0

    TDQS

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: execution, search, server listing, weight management, index refresh, and connection cleanup. There is no functional overlap between any pair of tools.

    Naming Consistency5/5

    All tool names follow a uniform verb-first snake_case pattern (e.g., execute_mcp_tool, list_available_mcps, reset_learned_weights). The verbs are action-oriented and consistently describe the operation.

    Tool Count5/5

    Seven tools is well-scoped for a proxy MCP server covering discovery, execution, learning, and maintenance. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The tool set covers all essential operations for the proxy's purpose: finding tools (search_tools, refresh_tool_index), executing tools (execute_mcp_tool), managing servers (list_available_mcps, close_mcp_connections), and controlling learning (get/reset_learned_weights). No significant gaps are evident.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues