Skip to main content
Glama
Sign In
semantic-code-mcp

semantic-code-mcp

by vrppaul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to semantic-code-mcp

No user-submitted related servers found.

    Related Servers

    • code-rag

      kkuppula
      F
      license
      Not graded
      quality
      C
      maintenance
      A semantic code search MCP server that enables natural language queries against your codebase, supporting features like related file discovery and context expansion, all running locally.
      2
      -

    • CodeLens MCP

      devprashant19
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that enables LLM clients like Claude to perform semantic code search and answer questions about a codebase using tree-sitter parsing and sqlite-vec vector storage.
      -

    • codebaxing

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

    • semantic-code-mcp

      huawang1258
      A
      license
      A
      quality
      C
      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

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools map to distinct operations: retrieval (search_code), bulk indexing (index_codebase), and inspection (index_status). The only overlap is that search_code auto-indexes and re-indexes changed files, but the description explicitly says to call index_codebase 'only to re-index everything', which resolves the boundary.

    Naming Consistency4/5

    All names are snake_case verb_noun (search_code, index_codebase, index_status), which is predictable. Minor deviation: index_status is a read-only getter sharing the 'index_' prefix with the mutating index_codebase, but the meaning is still clear.

    Tool Count4/5

    Three tools is lean but each earns its place for a focused code-search server: search, index, and status. Nothing looks padded or redundant, though the surface is on the thin side of the 3-15 sweet spot.

    Completeness4/5

    The search lifecycle (index, re-index, status, query with filters) is covered with no dead ends for its stated purpose. Gaps are minor: there is no explicit index deletion/reset tool, so force re-index is the only workaround, and no way to fetch chunks by file path without a query.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources