Skip to main content
Glama
shengxiao20

mcp-proxy

by shengxiao20

Related Servers

Alternatives to mcp-proxy

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A proxy MCP server that lazy-loads tools from configured servers on demand, reducing token usage and enabling mid-session server switching.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.
      126
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP proxy that reduces context bloat by exposing only relevant tools and compressing schemas, enabling efficient use of multiple MCP servers.
      19 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A proxy MCP server that manages multiple upstream MCP servers by grouping them and loading tool schemas on-demand, reducing LLM context usage.
      3,347 npm
      51
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A token-efficient MCP server that reduces context window bloat by lazy loading tool descriptions and proxying calls through three simple tools, with a dashboard for managing connections.
      3 npm
      9
      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

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: listing servers, listing/reading tools, calling tools, and cache refresh. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools use snake_case and follow a consistent verb_noun pattern (e.g., call_tool, list_servers). No deviations.

    Tool Count4/5

    5 tools cover the core proxy functionality. While minimal, it's reasonable for a proxy that relies on downstream servers. Could be expanded slightly for server management.

    Completeness4/5

    Core operations (listing servers, tools, calling, cache refresh) are present. Missing server add/remove or configuration, but the set is mostly complete for basic use.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues