knowledge-rag-mcp
Related Servers
Alternatives to knowledge-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search, deep-read, and build knowledge bases from Markdown, PDF, DOCX, and PPTX documents via MCP tools for retrieval, document navigation, and ingestion.15 npm653MIT
- AlicenseBqualityBmaintenanceEnables AI agents to discover, read, search, and install Markdown-based knowledge (rules, skills, workflows) from a local directory via MCP tools.14102 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to retrieve relevant context from local documents via MCP tools, supporting ingestion, semantic search, metadata filtering, and evidence inspection entirely on-device.MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search local repositories through hybrid keyword and embedding retrieval, read matched chunks, and list indexed repos via MCP, without API keys or cloud services.MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to search, read, and retrieve context from local knowledge bases with full-text search, absolute paths, and section-level details.4-
- AlicenseNot gradedqualityBmaintenanceEnables users to index and retrieve local documents through semantic, BM25, or hybrid search, with tools for chunk reads and page images accessible from MCP clients such as Codex and ChatGPT web.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct action in the RAG lifecycle: list, status check, preview, connect/index, search, and read. The preview/connect pair shares a resource but their descriptions clearly separate a read-only preview from a confirmed configuration step, so misselection is unlikely.
All tools follow a consistent snake_case verb_noun pattern (list_knowledge_bases, get_setup_status, preview_knowledge_base, connect_knowledge_base, search_knowledge, read_document). No mixed conventions or vague verbs.
Six tools map cleanly onto the setup-to-retrieval workflow with no filler. Each tool earns its place and the count is well-scoped for the domain.
The surface covers setup status, listing, preview, indexing/connect, search, and document read, which handles the core retrieval lifecycle. However, there is no way to disconnect/delete or reindex a knowledge base, leaving lifecycle management gaps an agent may hit.