Skip to main content
Glama

Related Servers

Alternatives to Code Search MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to perform high-performance code search and analysis across multiple languages using symbol indexing, regex text search, and structural AST pattern matching. It also provides tools for technology stack detection and dependency analysis with persistent caching for optimized performance.
      9
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables AI IDEs and coding agents to navigate code at the AST symbol level, perform surgical, collision-free refactoring, and resolve live library documentation. It also supports project onboarding memory, giving agents semantic precision without regex guesswork or heavy dependencies.
      5
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      A high-performance CLI tool that provides semantic code search, advanced architectural analysis, and codebase indexing with vector embeddings across multiple programming languages. Enables AI assistants to understand and navigate large codebases through graph-based relationships and intelligent code pattern detection.
      907
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables efficient codebase exploration with tools to list exports, get file outlines, read targeted regions, and find references without loading entire files.
      4
      7 npm
      1
      MIT

    TDQS

    A4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The tools have distinct primary purposes: view_code_items for precise retrieval of known items, view_files_full_context for panoramic analysis with auto-expansion, and view_files_outlines for structural exploration. However, view_files_full_context and view_files_outlines both involve file-level analysis and could be confused in some scenarios, though their descriptions clarify different focuses (context vs. outlines).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with 'view_' prefix and descriptive suffixes (code_items, files_full_context, files_outlines). The naming is uniform and predictable, making it easy to understand the tool set's structure at a glance.

    Tool Count4/5

    With 3 tools, the count is appropriate for a code search server, covering precise retrieval, contextual analysis, and structural outlines. It is slightly lean but reasonable, as each tool serves a clear and distinct function without obvious redundancy, though a few more specialized tools might enhance coverage.

    Completeness3/5

    The tools cover key aspects of code search and analysis, including retrieval, context, and structure, but there are notable gaps. For example, there is no tool for searching code by content (e.g., text search) or for updating/modifying code, which are common in code-related workflows. The surface is functional but incomplete for a full code interaction domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues