RAG-MCP
Related Servers
Alternatives to RAG-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceExposes a stdio MCP server that indexes a markdown vault (such as an Obsidian folder of notes) into SQLite FTS5 and answers BM25-ranked section-level queries, with filters for note type. It also exposes reindexing so notes edited on disk become searchable again, giving coding agents persistent, durable memory across sessions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables BM25 lexical search over a user-provided corpus of CTF writeups or technical documents through an MCP tool, returning relevant results with optional category and solved filters. It can run locally over stdio or as a centralized HTTP service shared by multiple MCP clients.MIT
- AlicenseNot gradedqualityFmaintenanceLocal-first Markdown vault retrieval for agents. Read-only MCP stdio server exposing search, get, status, and doctor over Obsidian-compatible Markdown with hybrid BM25/vector/wikilink/title retrieval and first-class CJK support.11MIT
- AlicenseNot gradedqualityBmaintenanceTurns any folder of PDFs, markdown, and text files into a local, queryable knowledge base exposed as an MCP server. Enables MCP-compatible agents to semantically search indexed documents, retrieve relevant passages with source and relevance scores, list or reindex documents, and inspect cache and token usage — instead of reading whole files into context.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP clients to query locally indexed code, docs, logs, JSONL/CSV and PDFs using BM25 full-text, vector and hybrid search, returning cited passages with file:line references instead of whole-file reads. Also supports code search, batch queries and persistent agent memory namespaces.17,802Apache 2.0
- AlicenseAqualityAmaintenanceLocal deterministic BM25 memory for AI agents — offline-first, no API key, SHA-256 content-addressed shards, stdio MCP transport. Same query always returns the same ranked result.1119 npmMIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: search returns ranked passages, get_chunk retrieves a specific chunk, get_document retrieves a full document, and list_documents provides an overview. There is no overlap or ambiguity between them.
All tool names follow the same verb_noun pattern with lowercase and underscores: search_documents, get_chunk, get_document, list_documents. The convention is perfectly consistent.
Four tools form a tight, well-scoped set for a RAG server. Each tool earns its place by covering the essential retrieval workflow without redundancy or bloat.
The tool surface covers the full retrieval lifecycle: discover what's indexed (list_documents), search the corpus (search_documents), read a specific passage (get_chunk), and read the full source (get_document). No obvious gaps exist for the stated purpose.