Skip to main content
Glama
damoqiongqiu

mcp-local-rag

by damoqiongqiu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-local-rag

No user-submitted related servers found.

    Related Servers

    • 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

    • rag-mcp

      MasihMoafi
      A
      license
      Not graded
      quality
      B
      maintenance
      A local hybrid-search MCP server that enables coding agents to query files and folders using natural language, returning relevant code chunks with exact source paths. Everything runs on-device with no API keys or network calls.
      5
      MIT

    • lynx-mcp

      lorenzo-cambiaghi
      A
      license
      A
      quality
      A
      maintenance
      A 100% local MCP server for semantic and lexical search over your code, library docs, and PDFs, featuring hybrid BM25 and dense retrieval, syntax aware chunking, and an optional code knowledge graph. It also ships a Coral integration, so you can expose your code search as SQL and join it with live data, all without anything leaving your machine.
      8
      16
      86 PyPI
      9
      Apache 2.0
    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 16 tools

    Disambiguation4/5

    Tools are largely distinct, but status and health_check both report on system state, and reindex_stale/reindex_all share a purpose though descriptions clarify the difference. Most tools target unique resource+action combinations (ingest, query, delete, list, config).

    Naming Consistency4/5

    Nearly all tools follow a verb_noun pattern in snake_case (query_documents, ingest_file, delete_file, reindex_stale). Exceptions like 'status' and 'config' are bare nouns, and 'dedup_check' reverses the order, but the overall pattern is predictable.

    Tool Count4/5

    16 tools is slightly above the typical 3-15 range but justified given the server's broad scope (ingestion, querying, index management, code analysis, configuration, health, export). Each tool serves a distinct purpose and the count feels reasonable for a full-featured RAG server.

    Completeness4/5

    The tool surface covers the core RAG lifecycle: multiple ingestion methods, querying with context reading, deletion, listing, reindexing (stale/all), deduplication, configuration, export, and health checks. Minor gaps exist, such as no explicit 'get_document' tool, but query_documents and read_chunk_neighbors provide adequate access. Code analysis is well-covered with find_definition and find_references.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources