docs-rag-mcp
Related Servers
Alternatives to docs-rag-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables semantic search over local markdown documentation by indexing files and ranking results using vector similarity and BM25 fusion.111 npmApache 2.0
- FlicenseAqualityCmaintenanceEnables AI assistants to search and retrieve content from local Markdown notes using term-frequency scoring.2-
- AlicenseNot gradedqualityBmaintenanceProvides structured, addressable access to a local markdown vault with heading-anchored fragments, BM25 search, and stable IDs for verifiable retrieval.10 npm2MIT
- AlicenseNot gradedqualityAmaintenanceBuilds a keyword-searchable index from markdown documentation bundles and serves it to LLM agents via MCP, with retrieval logging and reporting for curation.MIT
- AlicenseNot gradedqualityAmaintenanceServes local Markdown wikis as a read-only knowledge source with MCP tools for agent context retrieval.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables retrieval-augmented generation over a local markdown corpus, allowing grounded, cited answers via an MCP tool or CLI.9 npmMIT
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between overlapping tools. The purpose of search_docs is singular and clear.
The single tool name 'search_docs' follows a clear verb_noun pattern, which is consistent for the server's scope. There are no other names to compare, so it is perfectly consistent.
A single tool for a docs RAG server is borderline but acceptable, as search is the primary function. However, it feels slightly thin, and additional tools like list_docs or get_doc could enhance usability.
For a documentation search server, search_docs covers the core retrieval need. Minor gaps exist such as no ability to list available document sources or fetch a specific document directly, but these are not critical for basic RAG workflows.