Skip to main content
Glama

Related Servers

Alternatives to context-firewall

No user-submitted related servers found.

    Related Servers

    • 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
      Aggregates tools from multiple upstream MCP servers and exposes them through 4 meta-tools, enabling LLMs to discover and use hundreds of tools without loading all schemas upfront.
      2
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP proxy that bundles flat tool lists into hierarchical subcommand groups to reduce context token usage, supporting multi-server aggregation and auto-generated help from tool schemas.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Acts as a proxy/router for multiple downstream MCP servers, exposing only meta-tools to the host to reduce token usage, enabling efficient search and invocation of tools from a fleet of servers.
      10 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients of tool-heavy MCP aggregators to find and use upstream tools on demand through four fixed bridge tools (search, describe, call, refresh), cutting per-turn tool context from ~180k tokens to ~2–3k. It merges multiple upstream servers behind sticky sessions and a local lexical BM25 index, so only the schemas actually needed are retrieved.
      6
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing categories, searching tools, invoking tools, and reading more output. No overlap in functionality.

    Naming Consistency5/5

    All tools use consistent snake_case verb_noun pattern (list_tool_categories, search_tools, invoke_tool, read_more). Naming is predictable and clear.

    Tool Count5/5

    Four tools is well-scoped for a firewall/proxy server that mediates interactions with downstream servers. Each tool earns its place.

    Completeness4/5

    Covers the core proxy operations (list, search, invoke, read more). Minor gaps like batch operations or configuration tools are not critical for basic use.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive