llm.energy - Extract documentation for AI agents from any site with llms.txt support
Connect Extract Llms Docs to Claude, Cursor or any other MCP client and it stops being a tab you switch to. llm.energy - Extract documentation for AI agents from any site with llms.txt support. The extract llms docs mcp server is what makes that connection.
Extract llms.txt documentation and install.md instructions from any website for AI agents, LLMs, and automation workflows.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
extract_docs — Extract documentation from a URL with llms.txt supportvalidate_url — Check if a URL has llms.txt availableverify_llms_txt — Verify llms.txt exists and get file infodiscover_documentation_urls — Find documentation URLs for a domainlist_sites — Get directory of known llms.txt-enabled sitessearch_sites — Search the site directory by category or keywordConfiguration is passed through the environment: ADMIN_KEY, ANTHROPIC_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Extract Llms Docs's toolset — extract_docs, validate_url, verify_llms_txt and 3 more — is a fair guide to whether it matches your workflow. It is maintained by nirholas; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| extract_docs | Extract documentation from a URL with llms.txt support |
| validate_url | Check if a URL has llms.txt available |
| verify_llms_txt | Verify llms.txt exists and get file info |
| discover_documentation_urls | Find documentation URLs for a domain |
| list_sites | Get directory of known llms.txt-enabled sites |
| search_sites | Search the site directory by category or keyword |
| Variable | Description | Required |
|---|---|---|
| ADMIN_KEY | Credential the server authenticates with. | Yes |
| ANTHROPIC_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.