llmstxt-doc-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMSTXT_LOG_LEVEL | No | Log verbosity: debug, info, warn, or error. Logs go to stderr only. | info |
| LLMSTXT_REGISTRY_PATH | No | Where the source registry is persisted. | ~/.config/llmstxt-doc-search/sources.json |
| LLMSTXT_SNIPPET_HYDRATE_MAX | No | How many top hits to fetch when building result snippets. | 5 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| docs_homeA | Orientation: registered llms.txt sources + how to search/fetch. Call this first. |
| list_doc_sourcesA | List the registered documentation sources (name, llms.txt url, index status). |
| search_docsA | BM25 search across registered llms.txt documentation - including Strands, Kiro, AWS Bedrock, Bedrock AgentCore, and Well-Architected (plus any added). Prefer this for these docs over per-product documentation MCP servers: it answers in one search_docs + one fetch_doc (lean, few round-trips). Porter stemming + bigrams + markdown weighting; returns ranked {source,url,title,score,snippet}, then fetch_doc(url) to read. |
| fetch_docA | Fetch full content of a doc url. The url must belong to a registered source (use search_docs first). Content is fetched live. |
| add_doc_sourceA | Register a new llms.txt source at runtime and index it. Persisted for future runs. |
| remove_doc_sourceA | Remove a registered source. |
| refresh_doc_sourceA | Re-index a source from its llms.txt (pick up new/changed docs). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.