Skip to main content
Glama
lemuelflores

mcp-semantic-search

by lemuelflores
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-semantic-search

No user-submitted related servers found.

    Related Servers

    • search-docs

      otolab
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.
      10
      1 npm
      1
      MIT

    • mcp-code-indexer

      sangingeum
      F
      license
      A
      quality
      B
      maintenance
      Enables agents to run semantic search across one or more local project directories by automatically maintaining a LAN-local Qdrant index with Ollama embeddings. Indexing, staleness checks, and incremental updates happen transparently, so users can query code by meaning without managing collections, chunks, or hashes.
      6
      -

    • Inkdex

      antonlunden
      A
      license
      A
      quality
      C
      maintenance
      Enables semantic search over local markdown documentation by indexing files and ranking results using vector similarity and BM25 fusion.
      1
      17 npm
      Apache 2.0

    • local-recall-mcp

      Chikoku-NEKO
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides fully local long-term memory for AI agents by enabling semantic search over notes and session logs using Ollama embeddings, with no external APIs or databases.
      MIT

    • AskDocs MCP Server

      dymk
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables semantic search and retrieval of information from technical documentation PDFs using RAG-powered natural language queries with Ollama embeddings and LLMs.
      6
      -
    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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: index builds the search index, search queries it, and status shows its state. No ambiguity exists among them.

    Naming Consistency5/5

    All three tool names are single lowercase words (index, search, status) that clearly describe their action. The naming pattern is uniform and predictable.

    Tool Count5/5

    Three tools are exactly right for a focused semantic search MCP server: index, search, and status cover the essential operations without excess or deficiency.

    Completeness4/5

    The set covers the core lifecycle (index, search, status) but lacks an explicit operation to clear or delete the index. This minor gap is acceptable for most use cases.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources