Skip to main content
Glama

Related Servers

Alternatives to Context Mode

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that intelligently filters and compresses tool outputs to reduce context window usage, saving up to 90% of tokens by removing noise such as passing tests and redundant information.
      5
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that cuts cloud LLM costs 36-42% by indexing context locally and giving agents precision retrieval tools instead of raw context dumps.
      2 npm
      7
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that preserves LLM context by intercepting large data outputs and returning only concise summaries or relevant sections. It enables efficient sandboxed code execution, file processing, and documentation indexing across multiple programming languages and authenticated CLIs.
      11
      13,979 npm
      23,758
      Elastic 2.0
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Token-optimized MCP server that reduces context window usage by 59.5% by grouping 12 tools into 5 semantic operations, preserving all original functionality for AI assistants.
      9 npm
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools are largely distinct: execution (ctx_execute, ctx_execute_file, ctx_batch_execute), indexing (ctx_index, ctx_fetch_and_index), retrieval (ctx_search), and admin (ctx_stats, ctx_doctor, ctx_upgrade, ctx_purge, ctx_insight) form clear groups. The main ambiguity is between ctx_execute and ctx_execute_file (both run code, one inline vs. over a file), but descriptions and parameters make the distinction clear.

    Naming Consistency4/5

    All tools share the ctx_ prefix and snake_case, following an imperative verb pattern (ctx_execute, ctx_search, ctx_purge). Minor deviations like ctx_execute_file (noun modifier) and ctx_fetch_and_index (two verbs) are still readable and consistent with the overall style.

    Tool Count5/5

    11 tools is well-scoped for a server that handles sandboxed code execution, knowledge-base indexing/search, batch processing, and lifecycle administration. Each tool serves a distinct function without redundancy, and the count sits comfortably in the ideal 3-15 range.

    Completeness5/5

    The surface covers the full workflow: ingest (ctx_index, ctx_fetch_and_index), process (ctx_execute, ctx_execute_file, ctx_batch_execute), retrieve (ctx_search), monitor (ctx_stats), and maintain (ctx_purge, ctx_upgrade, ctx_doctor, ctx_insight). The only theoretical gap is fine-grained single-item deletion, but ctx_purge's scoped delete handles that adequately.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues