LLMSTXT-MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMSTXT_CONFIG | No | Path to custom configuration file (not implemented yet) | |
| LLMSTXT_TIMEOUT | No | Request timeout in seconds (default: 10) | 10 |
| LLMSTXT_ALLOWED_DOMAINS | No | Comma-separated list of allowed domains (default: * for all) | * |
| LLMSTXT_FOLLOW_REDIRECTS | No | Whether to follow HTTP redirects (true/false) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_doc_sourcesB | List all configured documentation sources |
| fetch_docsA | Fetch and parse documentation from a given URL or local file. Use this tool after list_doc_sources to:
Args: url: The URL to fetch documentation from. Returns: The fetched documentation content converted to markdown, or an error message if the request fails or the URL is not from an allowed domain. |
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 2 tools
The two tools serve clearly distinct purposes: listing configured sources versus fetching a specific documentation URL. There is no overlap or ambiguity about when to use each.
Both tool names follow a consistent verb_noun pattern (list_doc_sources, fetch_docs) using snake_case. The naming is predictable and readable.
With only two tools, the server feels minimal, though it may be appropriate for its narrow scope of listing sources and fetching docs. According to calibration, 1-2 tools is borderline thin, so this is not a strong score.
The tool surface covers the core workflow: list sources, fetch llms.txt or specific pages, and convert to markdown. A minor gap is the lack of a dedicated tool for managing sources (add/remove), but that appears to be configuration outside the server's purpose.