Skip to main content
Glama
Code Indexing MCP

Code Indexing MCP

by MarcinHamiga

Related Servers

Alternatives to Code Indexing MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides a local-first code indexing and search engine for coding agents via MCP, enabling precise codebase queries, symbol lookup, and freshness-aware retrieval.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI coding agents to index local codebases and search them by natural-language intent, find related files through imports and semantic similarity, and check indexing status. All processing runs locally via MCP tools.
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to index and search multi-project codebases through semantic and full-text retrieval, symbol lookup, and reference search via a local MCP endpoint.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local MCP server for semantic code search using Tree-sitter AST parsing, local embeddings, and hybrid search; enables indexing and querying codebases entirely offline.
      7
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first code indexer that provides deep code understanding for Claude and other LLMs with symbol/text search across 48+ languages, semantic search capabilities, and real-time index updates through the Model Context Protocol.
      59
      MIT

    TDQS

    C2/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools clearly target distinct actions: project lifecycle (init, index, status, list, remove) versus code querying (find_symbol, search_code, file_outline, get_chunk). init_project and index_project could be confused without descriptions, and find_symbol/search_code overlap slightly, but their intended scopes are still distinguishable.

    Naming Consistency4/5

    All names use lowercase snake_case with mostly verb_noun construction like init_project, list_projects, remove_project, search_code, and get_chunk. A couple are noun phrases such as project_status and file_outline, which deviate slightly from the dominant pattern, but the naming remains predictable and readable.

    Tool Count5/5

    Nine tools is well within the ideal range for a focused code-indexing server. Each tool covers a necessary part of the workflow: project setup, indexing, status, discovery, removal, and code retrieval/exploration.

    Completeness4/5

    The tool surface covers the main project lifecycle and core code-search/exploration needs. Obvious gaps like symbol references, project updates, or index rebuilding are minor and can typically be worked around using the existing tools.