Skip to main content
Glama

Related Servers

Alternatives to Context Mode

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides a persistent sandbox for AI coding agents to explore codebases server-side, returning only compact summaries to reduce context consumption.
      3
      20 PyPI
      8
      MIT
    • 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
      C
      quality
      A
      maintenance
      An MCP server that filters and compresses context by 80-90% before sending to an LLM, using code knowledge graphs and compression.
      20
      100 PyPI
      2
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      60 npm
      6
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides reversible context compression for AI agents, reducing token usage while preserving the ability to retrieve original content, and serves as an MCP server for integration with tools like GitHub Copilot and Claude Code.
      3
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP server that gives LLMs long-term memory by indexing code, infrastructure, logs, and docs into a queryable graph. It enables semantic and structural search, evidence-backed reasoning, and tracked plans that persist across sessions and teams.
      1
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    ctx_execute, ctx_execute_file, and ctx_batch_execute share an execution surface, but each has a clearly scoped role (single code block vs file-scoped processing vs batched commands with auto-indexing) reinforced by detailed WHEN/WHEN NOT guidance. ctx_index and ctx_fetch_and_index are similarly distinct (inline content vs URL fetching). No two tools are truly interchangeable.

    Naming Consistency5/5

    Every tool uses the ctx_ prefix with lowercase snake_case, and most follow a verb pattern (ctx_execute, ctx_index, ctx_search, ctx_purge, ctx_upgrade) or a noun for informational tools (ctx_stats, ctx_doctor, ctx_insight). Fetch-and-index and batch-execute combine verbs in a predictable, readable way.

    Tool Count5/5

    11 tools cover the server's scope — sandboxed execution, knowledge-base indexing/retrieval, maintenance (doctor, upgrade), statistics, and destructive cleanup — without redundancy. Each tool has a distinct purpose, and the count is within the ideal range for a feature-rich but focused MCP server.

    Completeness4/5

    The main lifecycle is covered: capture (ctx_execute/ctx_execute_file/ctx_batch_execute/ctx_fetch_and_index), store (ctx_index), retrieve (ctx_search), and destroy (ctx_purge). Minor gaps remain: there is no per-source or per-chunk deletion/update tool, and no explicit way to list all indexed sources beyond stats counts.

    Maintenance

    ActivityActive
    ResponsivenessResponsive