Allows fetching and processing Modal's documentation via the llms.txt standard, converting content to clean Markdown.
Provides access to Next.js documentation by fetching and converting its llms.txt file into Markdown.
Provides access to Node.js documentation by fetching and converting its llms.txt file into Markdown.
Allows fetching and processing NVIDIA's documentation via the llms.txt standard, converting content to clean Markdown.
Provides access to React documentation by fetching and converting its llms.txt file into Markdown.
Allows fetching and processing Supabase's documentation via the llms.txt standard, converting content to clean Markdown.
A Model Context Protocol (MCP) server that provides access to LLMS.TXT documentation files. This server allows AI agents to fetch and process documentation from various sources.
Multiple Documentation Sources: Access documentation from React, Next.js, Node.js and more
HTTP Fetching: Fetch documentation from any HTTPS URL with domain restrictions
HTML to Markdown: Automatically converts HTML content to clean Markdown
Environment Configuration: Customize behavior via environment variables
MCP Protocol: Full Model Context Protocol compliance
Related MCP server: MCP LLMS-TXT Documentation Server
npm install -g @pinkpixel/llmstxt-mcpThe server starts automatically and provides two tools:
list_doc_sources - Lists all configured documentation sources
fetch_docs - Fetches documentation from a URL and converts to Markdown
By default, the server is configured with:
React documentation: https://react.dev/llms.txt
Next.js documentation: https://nextjs.org/llms.txt
Node.js documentation: https://nodejs.org/llms.txt
LLMSTXT Directory (Cloud): https://directory.llmstxt.cloud/ - Curated directory of companies using llms.txt
LLMSTXT Site Directory: https://llmstxt.site/ - Comprehensive list with token counts and stats
The two directory sources provide access to thousands of websites that have adopted the llms.txt standard:
directory.llmstxt.cloud - Curated directory with companies like Anthropic, Supabase, Modal, NVIDIA, and many others across AI, developer tools, finance, and products categories
llmstxt.site - Comprehensive searchable directory with detailed statistics and token counts for each llms.txt file
These directories are invaluable for discovering documentation from the growing ecosystem of companies adopting the llms.txt standard.
Customize behavior with these environment variables:
LLMSTXT_CONFIG: Path to custom configuration file (not implemented yet)
LLMSTXT_FOLLOW_REDIRECTS: Whether to follow HTTP redirects (true/false)
LLMSTXT_TIMEOUT: Request timeout in seconds (default: 10)
LLMSTXT_ALLOWED_DOMAINS: Comma-separated list of allowed domains (default: * for all)
Example:
export LLMSTXT_FOLLOW_REDIRECTS=true
export LLMSTXT_TIMEOUT=30
export LLMSTXT_ALLOWED_DOMAINS="react.dev,nextjs.org,nodejs.org"You can install globally with npm i -g @pinkpixel/llmstxt-mcp and then it can be ran with "llmstxt-mcp"
Add to your mcp_config.json:
{
"mcpServers": {
"llmstxt": {
"command": "llmstxt-mcp",
"env": {
"LLMSTXT_FOLLOW_REDIRECTS": "true",
"LLMSTXT_TIMEOUT": "30"
}
}
}
}OR use with npx
{
"mcpServers": {
"llmstxt": {
"command": "npx",
"args": ["-y", "@pinkpixel/llmstxt-mcp", "llmstxt-mcp"],
"env": {
"LLMSTXT_FOLLOW_REDIRECTS": "true",
"LLMSTXT_TIMEOUT": "30"
}
}
}
}# Build first
npm run build
# Test with inspector
npm run inspector
# Or directly
npx @modelcontextprotocol/inspector ./build/index.js# List available tools
npx @modelcontextprotocol/inspector --cli ./build/index.js --method tools/list
# List doc sources
npx @modelcontextprotocol/inspector --cli ./build/index.js --method tools/call --tool-name list_doc_sources
# Fetch documentation
npx @modelcontextprotocol/inspector --cli ./build/index.js --method tools/call --tool-name fetch_docs --tool-arg url="https://example.com"Domain Restrictions: Configure allowed domains via environment variables
HTTPS Recommended: Always use HTTPS URLs when possible
No Local Files: Current version only supports HTTP/HTTPS URLs
# Clone the repository
git clone https://github.com/pinkpixel-dev/llmstxt-mcp.git
cd llmstxt-mcp
# Install dependencies
npm install
# Build the server
npm run build
# Test with inspector
npm run inspectorThe server provides detailed error messages for:
Invalid or unreachable URLs
Domain restriction violations
Timeout errors
HTTP errors (404, 500, etc.)
MIT License - see LICENSE file for details.
Made with ❤️ by Pink Pixel
Fetch and parse documentation from a given URL or local file.
Use this tool after list_doc_sources to:
First fetch the llms.txt file from a documentation source
Analyze the URLs listed in the llms.txt file
Then fetch specific documentation pages relevant to the user's question
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.
Inputs: url (required).
List all configured documentation sources
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Turn any public website into an MCP server for agents to search, read and navigate.
MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API
Document-to-Markdown MCP server — convert PDF, Office and HTML into LLM-ready Markdown.
MCP server for agentverse documentation, generated by doc2mcp.