mcp-local-rag
Related Servers
Alternatives to mcp-local-rag
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server that enables local hybrid semantic and keyword search over private PDF, DOCX, Markdown, and text documents without sending data to embedding APIs.92,150 npmMIT
- AlicenseAqualityAmaintenancePrivacy-first local document search using semantic search. Runs entirely on your machine with no cloud services, supporting PDF, DOCX, TXT, and Markdown files.92,150 npm415MIT
- AlicenseAqualityBmaintenanceEnables any MCP client to index files, directories, and arbitrary text into a local SQLite-backed vector database and perform semantic search with language-aware chunking, filters, and context expansion, all offline without network calls.10MIT
- AlicenseAqualityDmaintenanceA local-first document retrieval MCP server that enables AI coding tools like Codex to search private local documents via semantic search and keyword boost, supporting ingestion of PDF, DOCX, TXT, Markdown, and HTML files.7MIT
- AlicenseAqualityBmaintenanceEnables natural-language semantic search over your own local files through an MCP server, fully offline without API keys or a server daemon, with optional LLM-grounded answers and exact file:line sources.5MIT
- AlicenseAqualityAmaintenanceSemantic code search for any MCP client: indexes local folders of code and docs and answers plain-language or code queries with matching passages, file paths, line ranges and scores. Embedding runs on the local CPU with the Motherlode code-search encoder, so no file content leaves the machine; the encoder downloads once from Hugging Face. Install: npx -y blackwindow-weave-mcp.6430 npmBusiness Source 1.1
TDQS
Scored across 9 tools
Each tool has a distinct purpose: ingest_file vs ingest_data are cleanly split by path vs in-memory string, delete_file consolidates deletion for both, query_documents is search, read_chunk_neighbors is follow-up context, and sync_start/sync_status form a clear job/poll pair. list_files and status both give overviews but their descriptions clearly separate file scanning from index metrics.
Most tools follow a consistent verb_noun pattern (query_documents, ingest_file, ingest_data, delete_file, list_files, read_chunk_neighbors, sync_start, sync_status). The lone 'status' noun breaks the pattern, and sync_ prefix is a minor variant, but overall it reads predictably.
Nine tools is well-scoped for a local RAG server, with each tool earning its place across search, ingest, delete, listing, status, context retrieval, and sync operations. No redundancy or bloat.
The surface covers the RAG lifecycle well: create/update via ingest and re-ingest, read via query and chunk neighbors, delete, list, status, and disk reconciliation via sync. Minor gaps exist (no explicit whole-index reset or single-document metadata fetch), but agents can work around them via delete_file and query_documents.