knowledge-rag
Related Servers
Alternatives to knowledge-rag
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceA lightweight RAG (Retrieval-Augmented Generation) system for Claude Code that enables semantic search over local markdown documents via MCP tools, saving tokens and time.63-
- AlicenseNot gradedqualityCmaintenanceA modular RAG server with hybrid search and LLM rerank, exposing 3 MCP tools for AI clients like Claude Desktop and Cursor.MIT
- AlicenseAqualityAmaintenanceA 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.1679 npm13MIT
- AlicenseAqualityAmaintenanceUnified MCP server combining hybrid search (vector + BM25 + code graph), structural code analysis, and persistent semantic memory. 15 tools, 25+ languages, <350MB RAM, fully local.10MIT
- AlicenseAqualityBmaintenancePersistent 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.1628 npm7MIT
- AlicenseAqualityCmaintenanceSemantic vector DB as an MCP server for Claude Code — SQLite + FTS5 + local ONNX embeddings. Gives Claude persistent, searchable project knowledge across conversations.12MIT
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose: search, fetch full document, list, CRUD operations, URL import, and index maintenance. The two status/stat tools (get_reindex_status, get_index_stats) are separate and non-overlapping. No ambiguity between search and retrieval, or between add and update.
Most tools follow a consistent verb_noun pattern (search_knowledge, add_document, update_document, remove_document, list_categories, list_documents). Minor deviation with 'add_from_url' which mixes source into the name, and 'evaluate_retrieval' which is a compound but still understandable. Overall the naming is predictable and clear.
13 tools is a reasonable number for a knowledge base management system, covering search, document CRUD, URL import, reindexing, and evaluation. This is within the ideal 3-15 range and not excessive or sparse.
The tool set covers the full lifecycle: adding (via text or URL), updating, deleting, searching, retrieving, listing, reindexing, and quality evaluation. There's no obvious missing functionality for a RAG knowledge base. The inclusion of evaluate_retrieval and index stats adds operational completeness.