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
      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
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight and fast MCP server that enables AI agents to efficiently discover and execute tools through progressive disclosure, minimizing context consumption while supporting safe code execution in external environments.
      6
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
      3
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A generic MCP proxy that filters which tools are exposed from a remote MCP server, reducing context window token usage by only loading the tools you actually need.
      16
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A single MCP endpoint for AI agents to browse, inspect, and call tools from multiple upstream MCP servers without loading all schemas upfront, reducing context overhead.
      8
      ISC

    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