knowledge-rag
Related Servers
Alternatives to knowledge-rag
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceA lightweight RAG (Retrieval-Augmented Generation) system for Claude Code that enables semantic search over local markdown documents via MCP tools, saving tokens and time.64-
- AlicenseNot gradedqualityDmaintenanceA modular RAG server with hybrid search and LLM rerank, exposing 3 MCP tools for AI clients like Claude Desktop and Cursor.MIT
- AlicenseAqualityCmaintenanceA fully local RAG MCP server for semantic code search and code intelligence, using AST-level chunking and hybrid search to pinpoint functions, classes, and APIs. No cloud, no API keys, zero setup.1651 npm13MIT
- AlicenseAqualityAmaintenanceUnified MCP server: hybrid search + code graph + semantic memory. 10 tools, <350MB RAM, fully local. No API keys.8PolyForm Noncommercial 1.0.0
- AlicenseAqualityCmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.1630 npm7MIT
- AlicenseAqualityCmaintenanceSemantic vector DB as an MCP server for Claude Code — SQLite + FTS5 + local ONNX embeddings. Gives Claude persistent, searchable project knowledge across conversations.1225 PyPIMIT
TDQS
Scored across 13 tools
Each tool targets a distinct action/resource: browsing (list_documents, list_categories), retrieval (search_knowledge, search_similar, get_document), ingestion (add_document, add_from_url), mutation (update_document, remove_document), and maintenance (reindex_documents, get_reindex_status, get_index_stats, evaluate_retrieval). The descriptions explicitly cross-reference sibling tools to steer selection (e.g., search_similar vs search_knowledge, get_document vs search_knowledge). No two tools appear to do the same thing.
All 13 tools follow a consistent snake_case verb_noun pattern (list_*, get_*, add_*, search_*, update_*, remove_*, reindex_*, evaluate_*). Naming aligns cleanly with the underlying operation and resource, with no mixed conventions or vague verbs.
13 tools sits squarely in the ideal 3-15 range for a RAG knowledge-base server. The set covers browsing, searching, ingestion, lifecycle mutation, and operational maintenance without redundant or filler tools.
Full lifecycle is covered: create (add_document, add_from_url), read (list_documents, get_document, search_knowledge, search_similar, list_categories), update (update_document), delete (remove_document), plus reindex/maintenance (reindex_documents, get_reindex_status, get_index_stats) and quality auditing (evaluate_retrieval). No obvious dead ends for the stated domain.