Skip to main content
Glama

Related Servers

Alternatives to CodeRAG

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables Claude Code and AI coding agents to retrieve compact, task-shaped code evidence bundles via MCP, combining AST-aware retrieval, hybrid BM25+FAISS search, call-graph traversal, reranking, and token-budgeted context assembly.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to navigate and understand entire codebases through symbol-aware semantic retrieval and relational call graph traversal, supporting structural impact analysis and code modification workflows over MCP.
      Apache 2.0
    • A
      license
      B
      quality
      A
      maintenance
      Enables coding agents to retrieve the most relevant code for a task within a hard token budget by fusing code graph, BM25, local embeddings, and git history, and to navigate symbols, callers, impact, and related files. It runs locally over MCP with no API keys and keeps its index fresh.
      10
      28 PyPI
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to perform hybrid code search, get explanations, analyze relations and impacts, retrieve context packs, and generate documentation across ~45 languages via 17 MCP tools, all powered by a local vector database and LLM.
      2
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to query a semantic code graph over MCP, retrieving exact function source, definitions, callers/callees, impact analysis, and minimal test selection instead of whole files.
      14
      Apache 2.0

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the RAG workflow: indexing, status, searching, context retrieval, and impact analysis. search_code and get_context both retrieve code, but get_context explicitly adds citations and call-graph expansion, so they are clearly separated.

    Naming Consistency4/5

    All names use snake_case and follow a command-like style. However, status is a bare noun rather than verb_noun, and impact_radius is a noun phrase while others start with verbs (index, search, get). Minor deviations but overall predictable.

    Tool Count5/5

    Five tools is well-scoped for a code RAG server: one tool to build the index, one for health/size, one for basic search, one for context-rich retrieval, and one for dependency impact. No unnecessary tools.

    Completeness4/5

    The core lifecycle is covered: index creation, search, context extraction, and impact analysis. Missing explicit delete/re-index or list available repositories, but these are minor gaps for a focused RAG use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues