llmstxt-doc-search
Related Servers
Alternatives to llmstxt-doc-search
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAggregates documentation from multiple sources (llms.txt format or web scraping) and provides semantic search capabilities using vector embeddings and hybrid search for each documentation source.68 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables fast, token-efficient access to large documentation files in llms.txt format through semantic search. Solves token limit issues by searching first and retrieving only relevant sections instead of dumping entire documentation.3MIT
- FlicenseAqualityCmaintenanceGives an LLM client BM25 keyword search over a local corpus of Markdown and text files, letting it find ranked passages, fetch exact chunks with source offsets, read whole documents, and list what was indexed. It runs entirely locally over stdio with an in-memory index, calling no model and requiring no API key.4-
- AlicenseAqualityCmaintenanceEnables LLM hosts to retrieve live, relevant documentation excerpts from official library docs sites via a search-and-RAG tool, avoiding reliance on training data.1MIT
- AlicenseAqualityAmaintenanceWeb search (embedded SearXNG), content extraction, and library docs indexing with hybrid search. No API keys required.61,488 PyPI18Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to discover the llms.txt index covering any site, fetch its linked documentation pages as markdown, and search across parsed indexes by section heading, link title, and notes.MIT
TDQS
Scored across 7 tools
Each tool serves a distinct role: orientation, listing sources, searching, fetching content, and adding/removing/refreshing sources. There is no overlap in purpose, so an agent can easily choose the right tool.
Most tools follow a clear verb_noun pattern (list_doc_sources, search_docs, fetch_doc, add_doc_source, etc.). The exception is docs_home, which is a noun identifier, and there are minor singular/plural inconsistencies (doc vs docs), but the overall style is consistent.
Seven tools is well-scoped for a documentation search server, covering both source management and retrieval operations without unnecessary bloat.
The set provides full lifecycle coverage: add/list/remove/refresh sources, search across them, and fetch full content. No obvious missing operations for the stated purpose.