Skip to main content
Glama

Related Servers

Alternatives to MCP Gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A unified gateway and web dashboard that aggregates multiple MCP servers into a single Streamable HTTP endpoint. It supports stdio, SSE, and HTTP protocols, featuring optimized tool exposure modes to reduce token consumption for AI clients.
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A universal gateway that aggregates multiple MCP servers into a single interface while providing advanced token optimization, result filtering, and automated summarization. It enables efficient management of large tool catalogs and reduces context usage by up to 95% for major AI clients.
      13 npm
      15
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server gateway that reduces context bloat through progressive tool discovery and Lua-based tool chaining, while centralizing multiple MCP servers into a single endpoint.
      15
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      A single MCP server gateway that reduces context bloat by providing progressive tool discovery and invocation, dynamically provisioning downstream servers on demand.
      26
      20
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.
      16 npm
      10
      Apache 2.0

    TDQS

    A4/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. For example, gateway_list_tools lists tools, gateway_search_tools searches them, gateway_invoke invokes them, and gateway_get_stats provides usage statistics. Tools like gateway_kill_server and gateway_revive_server are complementary but distinct in their actions (disable vs. re-enable).

    Naming Consistency5/5

    All tools follow a consistent 'gateway_verb_noun' pattern, such as gateway_list_servers, gateway_set_profile, and gateway_reload_config. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count5/5

    With 15 tools, the count is well-scoped for a gateway server that manages backend servers, routing, and monitoring. Each tool serves a specific function in this domain, such as listing, searching, invoking, and controlling servers, without being excessive or insufficient.

    Completeness5/5

    The tool set provides complete coverage for gateway operations, including server management (list, kill, revive), tool discovery (list, search), invocation, routing control (profiles), monitoring (stats, cost reports), and configuration (reload). There are no obvious gaps, enabling agents to handle all typical gateway workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive