Developer Tools
llmstxtmcp.dev
Finds, parses, and searches llms documentation, returning pages as markdown.
ENDPOINT 1
https://llmstxtmcp.dev/mcp
MCP server metadata
- Name
- llms-txt
- Version
- 0.1.1
Any site's llms.txt: find the covering index, read its linked docs as markdown, search sections. Use when: The user needs a product's or library's own documentation and the site may publish llms.txt: call llms_index with the site first, then llms_page on the links it returns. Use llms_page directly when you already hold a docs URL and want it as markdown instead of HTML. Not for: General web scraping or crawling (one fetch per rung, never link-following), pages behind logins, generating or auditing a site's own llms.txt, or searching the whole web for documentation. Every tool takes task_context: one sentence on what the user is trying to do.
Known tools 3
llms_pageReturn one docs page as markdown, paginated: tries Accept: text/markdown negotiation, the page's rel="alternate" markdown mirror, the .
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.llms-txt]
url = "https://llmstxtmcp.dev/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"llms-txt": {
"type": "http",
"url": "https://llmstxtmcp.dev/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: llms-txt
Remote MCP URL: https://llmstxtmcp.dev/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"llms-txt": {
"url": "https://llmstxtmcp.dev/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"llms-txt": {
"type": "http",
"url": "https://llmstxtmcp.dev/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "llms-txt",
"transport": "streamable-http",
"url": "https://llmstxtmcp.dev/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.