Skip to main content
Glama

Related Servers

Alternatives to Agent MCP Gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to use many MCP servers without context bloat by exposing meta-tools (search, load, call, run_code) that reduce token usage via progressive disclosure and result trimming.
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables teams to govern agent tool access by onboarding remote MCP servers, setting function-level allow lists and credential modes, and exposing permitted tools through a unified MCP endpoint with search and execute functions.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Acts as a proxy for multiple MCP servers, reducing context window usage from 15,000+ tokens to ~500 tokens by dynamically loading servers on-demand and exposing only 3 tools instead of all tool definitions.
      5
      GPL 3.0
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables organizations to govern agent tool access by onboarding remote MCP servers, defining function-level allow lists and credential modes, and exposing permitted tools through a single unified MCP endpoint with search and execute functions.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables teams to govern which tools agents can use by onboarding remote MCP servers with function-level allow-lists and org-shared or per-user credentials, then exposing permitted tools through a single unified endpoint with just search and execute functions. Keeps IDE context lean while enforcing permissions and auditing every tool call.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables teams to govern which tools agents can use by onboarding remote MCP servers, setting credential modes and function-level allow lists, and exposing permitted tools through a unified endpoint with search and execute functions.
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing servers, discovering tools on a server, executing tools, and checking gateway status. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (execute_tool, get_gateway_status, get_server_tools, list_servers).

    Tool Count5/5

    With 4 tools covering discovery and execution for a gateway, the count is well-scoped and appropriate for the server's purpose.

    Completeness5/5

    The tools provide a complete workflow: list servers, discover tools, and execute them, with an additional status tool. No obvious gaps for a gateway.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues