Local RAG
Related Servers
Alternatives to Local RAG
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables semantic search over personal files using natural language, with optional AI summarization, all running locally.-
- FlicenseAqualityDmaintenanceEnables indexing local documents (PDF, Markdown, text, code) into a knowledge base and querying them via semantic search using local embeddings, all running privately on your machine.4-
- AlicenseNot gradedqualityCmaintenanceLocal offline semantic search over documents (txt, md, pdf, docx, pptx, csv). Indexes folders into a LanceDB vector database with multilingual embeddings and supports hybrid vector + keyword search via Reciprocal Rank Fusion. No API keys, no cloud, no Docker required.29AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceSemantic search and retrieval system for local documents using vector embeddings, enabling AI-powered search across your document collections with support for multiple embedding providers.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language semantic search over a fully local knowledge base, keeping embeddings, storage, and retrieval on the machine.MIT
- FlicenseNot gradedqualityDmaintenanceEnables semantic search over local notes and documents using natural language queries. Supports multiple file types (Markdown, Python, HTML, JSON, CSV, text) with fast local embeddings and persistent ChromaDB vector storage.1-
TDQS
Scored across 9 tools
Each tool targets a distinct operation: ingestion, querying, neighbor context, deletion, listing, status, and sync lifecycle. The only similar pair, ingest_data and ingest_file, is clearly differentiated by input type (string vs. file path), and sync_start versus sync_status cleanly separates starting from monitoring.
Most names follow a consistent verb_noun pattern in snake_case: query_documents, delete_file, ingest_data, ingest_file, list_files, read_chunk_neighbors, sync_start, sync_status. The single 'status' tool breaks the pattern by being a bare noun rather than get_status or similar, which is a minor inconsistency.
Nine tools is well within the ideal range for a focused local RAG server. Each tool covers a meaningful, non-redundant capability—ingest, query, delete, list, context expansion, status, and sync—without bloat or excessive granularity.
The server covers the core RAG lifecycle: ingestion (file and data), retrieval, context expansion, deletion, listing, status, and filesystem reconciliation. A minor gap is that there is no direct way to fetch a document's chunks by filePath without first obtaining a chunkIndex from query_documents, but this is workable through existing tools.