fetch_llms_txtLABSCO SUMMARY
Checking for `llms.txt` first is the whole efficiency argument.
When a site publishes one, its documentation arrives as a curated index instead of a crawl, which is faster and far less noisy; when it does not, the discovery tool falls back to finding the documentation URLs.
What it is
A documentation-extraction service with an MCP surface. It checks whether a domain publishes an llms.txt file — the emerging convention for machine-readable documentation indexes — fetches it or its full variant, extracts documentation from an arbitrary URL with that support taken into account, and discovers documentation URLs for domains that have not adopted the convention. It also keeps a searchable directory of sites known to publish one.
What you get
- Documentation extracted from a URL with
llms.txtsupport applied when the site has one —extract_documentation - A domain checked for
llms.txtbefore you spend anything on crawling it, with the file's details reported —verify_llms_txt - The file itself fetched, in the short or the full form —
fetch_llms_txt,fetch_llms_full_txt - Documentation URLs discovered for a domain that does not publish one —
discover_documentation_urls - The same capabilities over REST, including
POST /api/extractandPOST /api/generate-install, which generates an install guide from a GitHub repository or a documentation URL
Requirements
Nothing to authorise. Connect to the hosted HTTP endpoint https://modelcontextprotocol.name/mcp/extract-llms-docs, which serves five tools — fetch_llms_txt, fetch_llms_full_txt, extract_documentation, verify_llms_txt and discover_documentation_urls. There is no local package to run instead: the README's @llm-energy/mcp-server is not on npm, and the published llms-forge 1.0.6 ships no command to launch. The repository is registered as io.github.nirholas/extract-llms-docs.
Setup effort
Add the hosted endpoint — paste it into your client
USE CASES
Getting a library's docs into a conversation
Check the domain for llms.txt, fetch it if present, and extract from the URL otherwise — without crawling a whole site.
Working with a site that has not adopted the convention
Run URL discovery for the domain to find where the documentation actually lives, then extract from there.
Deciding whether a fetch is worth it
Validate the URL and read the file's details first, so you know what you are about to pull before you pull it.
5 tools
Listed in project docs. Your client may show a different list.
fetch_llms_full_txtextract_documentationverify_llms_txtdiscover_documentation_urlsBEFORE YOU INSTALL
What to know first
Tools you get
5 tools named in the project's documentation.
Where it runs
The documented client connects to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
https://modelcontextprotocol.name/mcp/extract-llms-docsAdd this hosted endpoint to your MCP client.
MCP Clients
SperaxOS
{
"mcpServers": {
"extract-llms-docs": {
"type": "http",
"url": "https://modelcontextprotocol.name/mcp/extract-llms-docs"
}
}
}