Summary
Docs as resources, not as pasted text.
The distinction matters for clients that treat resources differently from tool output: the documentation is something you attach when it is relevant, rather than something a tool call dumps into the transcript. It is a small server with a correspondingly small setup — one command, one environment variable, no account.
What it is
A server for the Awesome-llms-txt collection. It surfaces those documentation files as MCP resources, so the docs for a library can be attached to a conversation directly rather than pasted in.
What you get
- Documentation from the Awesome-llms-txt collection, available as resources a client can attach
- No API keys and no secrets — the sample config in the README needs no edits before it works
- Runs straight from PyPI with uvx, so there is nothing to build
Requirements
The Python package mcp-llms-txt, version 0.2.0, launched as `uvx mcp-llms-txt`. Set PYTHONUTF8 to 1 in the server's environment. There is nothing to authenticate against.
Setup effort
One command — uvx mcp-llms-txt