Skip to main content
Glama
michaelkrauty

mcp-codesearch

by michaelkrauty
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-codesearch

No user-submitted related servers found.

    Related Servers

    • codebaxing

      duysolo
      A
      license
      A
      quality
      F
      maintenance
      MCP server for semantic code search that indexes your codebase and allows AI editors to search using natural language queries.
      9
      12 npm
      53
      MIT

    • codesteer-atlas

      LuisCarlosLopes
      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.
      5
      MIT

    • Tea Rags MCP

      artk0de
      A
      license
      Not graded
      quality
      A
      maintenance
      A high-performance MCP server for semantic search and codebase indexing using the Qdrant vector database. It features optimized embedding pipelines, AST-aware chunking, and git metadata enrichment for fast, privacy-focused local or remote search.
      15 npm
      11
      MIT

    • semantic-code-mcp

      huawang1258
      A
      license
      A
      quality
      B
      maintenance
      A self-hosted semantic code retrieval MCP server that enables natural language queries to find relevant code snippets using Tree-sitter AST parsing, embedding, and hybrid search with reranking.
      1
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool targets a distinct action: index discovery, deletion, cleanup, status, reindex, vocabulary repair, preview, and five clearly differentiated search modes (semantic, multi-repo, changed-files, similar-snippet, and symbol references). Delete_collection and cleanup_orphans both delete indexes, but their explicit vs. automatic orphan-detection purposes are clearly separated by the descriptions.

    Naming Consistency4/5

    The set is mostly imperative snake_case verb_noun (list_collections, delete_collection, force_reindex, repair_vocabulary), but search tools mix conventions: code_search is noun-first while search_multiple/search_changed use a verb-first style, and index_status is a noun phrase. The inconsistency is minor and all names remain readable and predictable in context.

    Tool Count5/5

    Twelve tools is within the well-scoped range and each tool covers a distinct indexing or search need rather than bloating the surface. The variety of search entry points is justified by materially different query semantics and use cases.

    Completeness5/5

    The server covers the full lifecycle: auto-indexing/creation via search or force_reindex, status inspection, preview, deletion, orphan cleanup, and vocabulary repair. Search coverage is similarly complete with semantic, multi-repo, changed-file, similar-code, and reference lookup, leaving no obvious dead ends for code-search workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources