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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/praveenc/llmstxt-doc-search'
If you have feedback or need assistance with the MCP directory API, please join our Discord server