Skip to main content
Glama
rohithmahesh3

mcp-semantic-search

by rohithmahesh3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-semantic-search

No user-submitted related servers found.

    Related Servers

    • Acemcp

      qy527145
      A
      license
      A
      quality
      F
      maintenance
      Enables semantic code search across codebases with automatic incremental indexing. Searches return relevant code snippets with file paths and line numbers based on natural language queries.
      1
      803
      Apache 2.0

    • Acemcp

      yeuxuan
      A
      license
      A
      quality
      D
      maintenance
      Provides code repository indexing and semantic search capabilities, allowing natural language queries to find relevant code snippets with automatic incremental indexing and multi-language support.
      1
      11 npm
      359
      ISC

    • CodeGrok MCP

      dondetir
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic code search for AI assistants by indexing codebases with embeddings and Tree-sitter, returning relevant snippets via natural language queries.
      15
      MIT

    • Smart Coding MCP

      omar-haris
      A
      license
      A
      quality
      F
      maintenance
      Provides intelligent semantic code search using local AI embeddings, enabling natural language queries to find relevant code by meaning rather than exact keywords. Indexes codebases in the background with smart project detection and privacy-first local processing.
      6
      48 npm
      199
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    search_code and search_file are distinct (codebase vs specific file), but their names are similar and could be confused without careful reading. get_status and get_live_watch_status also target different subsystems but share a naming pattern. Other tools have clearly unique roles.

    Naming Consistency4/5

    Tools follow a verb_noun pattern with consistent snake_case (search_code, clear_index, start_live_watch). Verbs vary (search, get, clear, start, stop, index) but the pattern is predictable. Minor deviation: index_codebase uses verb+noun while others use search_/get_ prefixes, but it remains consistent in style.

    Tool Count5/5

    8 tools is well within the ideal range and each covers a necessary function for a semantic search server: indexing, searching, status, and lifecycle management. No redundant tools are present.

    Completeness4/5

    The server covers the core lifecycle: index (manual and watch), search (codebase and file), status (index and watcher), and clear. Missing is the ability to remove a specific file from the index or selectively reindex, but agents can clear and reindex as a workaround.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources