Skip to main content
Glama

Related Servers

Alternatives to repocontext

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides intelligent code context and analysis through semantic compression, AST parsing, and multi-language support. Offers 60-80% token reduction while enabling AI assistants to understand codebases through local analysis, OpenAI-enhanced insights, and GitHub repository integration.
      6
      10
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides structured, token-efficient code context for AI assistants by indexing codebases with AST-level analysis, supporting 17+ languages, enabling semantic search, call-site tracking, and PR attribution.
      40
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turn any codebase into an AI-readable neural map — with proof. Every claim linked to code anchors (line + SHA-256 hash), every context window optimized with greedy token budgeting, every session protected by drift detection. Tree-sitter indexing across 11 languages, cross-session learning, AI enrichment, and 28 MCP tools. Zero config — just connect and your AI agent remembers everything.
      11
      13
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Make any LLM a codebase expert instantly. Provides deep code intelligence through semantic search, architecture mapping, security analysis, and smart context that fits perfectly in token windows.
      MIT

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools are mostly distinct: read_file_outline focuses on a single file's AST skeleton, get_codebase_map provides a repository-wide symbol map, and extract_relevant_context selects relevant files. However, extract_relevant_context and get_codebase_map both involve repository-level analysis, creating some potential overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: extract_relevant_context, read_file_outline, get_codebase_map. The naming is clear, predictable, and uniform.

    Tool Count5/5

    Three tools is well-scoped for a code context extraction server. Each tool addresses a distinct granularity level (whole repository map, single file outline, relevant file selection) without unnecessary bloat.

    Completeness4/5

    The toolset covers the core workflow of navigating and extracting code context: mapping symbols, outlining files, and selecting relevant files. It could potentially benefit from a raw file-content reading tool, but the provided tools are sufficient for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues