search-docs
Related Servers
Alternatives to search-docs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, and traverse a local knowledge base of Markdown files using full-text search and relationship graph, reducing token usage.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search, retrieve, and browse Markdown documentation in a local folder, then answer questions with cited sources.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI models to seamlessly access and query local markdown technical documentation files, providing automatic documentation context without explicit prompting.105ISC
- AlicenseNot gradedqualityDmaintenanceGives AI agents full-text search over any Markdown/MDX documentation folder.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables agentic document retrieval over markdown, CSV, and JSONL using BM25 and tree navigation, without vector databases or embeddings, allowing AI agents to search, browse, and retrieve structured document sections.451MIT
- AlicenseAqualityCmaintenanceEnables local-first hybrid knowledge retrieval from authorized Markdown and plain-text files, combining full-text and vector search with reranking and traceable source references via a single search tool.1MIT
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: status checks, search, outline, index maintenance, related project management, initialization, and document retrieval. No two tools overlap in function or ambiguity.
Naming conventions are inconsistent. While get_* tools are consistent, index_status, index_purge, maintenance_repair, and init deviate from a uniform verb_noun pattern, mixing noun-first and bare verb forms.
10 tools is well within the ideal range for a search-docs server. Each tool covers a distinct aspect of the domain (search, indexing, project management, init) without redundancy.
The surface covers core operations but has gaps: no remove_related_project to complement add_related_project, and no explicit index rebuild tool (only mentioned as a post-repair step). Additionally, there is no direct way to list all documents beyond index status counts.