Skip to main content
Glama
sfrangulov

minirag-mcp

by sfrangulov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to minirag-mcp

No user-submitted related servers found.

    Related Servers

    • ragi

      SusuTawar
      A
      license
      A
      quality
      D
      maintenance
      Local-first RAG indexing and semantic search MCP server. Enables document retrieval and context-aware queries using local embedding models.
      3
      6 npm
      MIT

    • corpus-rag

      monahand1023
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for local RAG over personal notes, PDFs, and documents, enabling plain-English querying and hybrid search with multi-hop context expansion.
      MIT

    • mcp-local-rag

      xiuxiansk
      A
      license
      A
      quality
      C
      maintenance
      MCP server that enables local hybrid semantic and keyword search over private PDF, DOCX, Markdown, and text documents without sending data to embedding APIs.
      9
      5,156 npm
      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.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: querying, ingesting, syncing, reading, listing, deleting, and status reporting. The only potential overlap (read_file vs read_chunk_neighbors) is clearly differentiated by full-document vs context-window scope. No two tools perform the same action.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (ingest_file, query_documents, delete_file). Minor deviations include the bare noun 'status' and the sync_start/sync_status pair, but the overall style is consistent and predictable.

    Tool Count5/5

    11 tools is well-scoped for a RAG server. Each tool fills a necessary role in the ingestion, sync, query, and management lifecycle, with no redundancy or bloat.

    Completeness5/5

    The tool set covers the full lifecycle: ingest (file/data/url), sync (start/status), query, read (full/context), list, delete, and status. Re-ingesting acts as an update mechanism, and there are no obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources