MCP LLMS.txt Explorer
The MCP LLMS.txt Explorer server helps discover and analyze websites implementing the llms.txt standard.
Check websites: Verify if a website has llms.txt or llms-full.txt files by providing the URL
List compliant websites: Get structured data about websites with LLMS files, with filtering options
Parse and validate: Analyze llms.txt files for standard compliance
Integration: Works with Claude Desktop for seamless usage
Debugging support: Includes MCP Inspector for troubleshooting
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP LLMS.txt Explorer check if openai.com has an llms.txt file"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP LLMS.txt Explorer
A Model Context Protocol server for exploring websites with llms.txt files. This server helps you discover and analyze websites that implement the llms.txt standard.
Features
Resources
Check websites for llms.txt and llms-full.txt files
Parse and validate llms.txt file contents
Access structured data about compliant websites
Tools
check_website- Check if a website has llms.txt filesTakes domain URL as input
Returns file locations and validation status
list_websites- List known websites with llms.txt filesReturns structured data about compliant websites
Supports filtering by file type (llms.txt/llms-full.txt)
Related MCP server: llm-energy
Development
Install dependencies:
pnpm installBuild the server:
pnpm run buildFor development with auto-rebuild:
pnpm run watchInstallation
Installing via Smithery
To install mcp-llms-txt-explorer for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @thedaviddias/mcp-llms-txt-explorer --client claudeInstalling Manually
To use this server:
# Clone the repository
git clone https://github.com/thedaviddias/mcp-llms-txt-explorer.git
cd mcp-llms-txt-explorer
# Install dependencies
pnpm install
# Build the server
pnpm run buildConfiguration with Claude Desktop
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"llms-txt-explorer": {
"command": "node",
"args": ["/path/to/llms-txt-explorer/build/index.js"]
}
}
}For npx usage, you can use:
{
"mcpServers": {
"llms-txt-explorer": {
"command": "npx",
"args": ["-y", "@thedaviddias/mcp-llms-txt-explorer"]
}
}
}Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
pnpm run inspectorThe Inspector will provide a URL to access debugging tools in your browser.
License
This project is licensed under the MIT License—see the LICENSE file for details.
Available Tools
2 toolscheck_websiteC
Check if a website has llms.txt files
Inputs: url (required).
list_websitesB
List known websites with llms.txt files
Inputs: filter_llms_txt, filter_llms_full_txt.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: check_website verifies the presence of llms.txt files on a specific website, while list_websites retrieves a list of known websites that already have such files. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on the task.
Both tools follow a consistent verb_noun pattern (check_website and list_websites), using snake_case and clear action verbs. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With only two tools, the server feels under-scoped for exploring llms.txt files. While the tools cover basic checking and listing, there are likely missing operations such as fetching file contents, updating lists, or analyzing data, which limits the server's utility for comprehensive exploration.
The tool set is severely incomplete for an 'Explorer' server. It lacks essential operations like retrieving the actual llms.txt content, validating file structure, searching within files, or managing the list of websites. This creates significant gaps that will hinder agents from performing meaningful exploration tasks.
Maintenance
Related MCP Connectors
Read-only search and discovery for the international llms.txt directory maintained by llmsmap.me.
Checks whether a website has a usable llms.txt. Score 0–100. Free 3/day/IP, then ¥10.
Audit websites for AI search readiness and generate or validate llms.txt. Free quick check.
Crawls any website and generates a standards-compliant /llms.txt file and JSON-LD schema bundle.
Related MCP Servers
- AlicenseBqualityFmaintenanceA server that analyzes website performance using Playwright and Lighthouse, allowing LLMs to perform web performance analysis through the Model Context Protocol.25MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to extract, validate, and discover documentation from websites using llms.txt and install.md standards.26 npm35-
- AlicenseNot gradedqualityBmaintenanceEnables websites to expose a first-class interface for AI agents by providing read-only MCP tools like search_site and generating llms.txt discovery files.3 npm6MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, validate, and audit llms.txt files for websites, including checking against Google Lighthouse's Agentic Browsing requirements, via Streamable HTTP with no API key needed.8 npm2MIT