Summary
Documentation arrives as text worth reading rather than a page you have to strip first.
One tool, one job, and the conversion is the whole value: structure and links survive, so the model can cite where something came from and follow a reference onward instead of hitting a dead end. The cookies file is the one concession to reality — the pages worth reading are often the ones behind a login.
What it is
A single-tool server that fetches a web page and converts it to Markdown with links and structure preserved.
What you get
- A page fetched and converted to clean Markdown, with its links intact so a documentation trail can still be followed
- More than one page handled in a call, through the pages parameter
- A cookies file pointed at, which puts pages that require a session within reach
Requirements
A URL. Nothing to configure and no key. Pages behind a session need a cookies file already on disk for cookiesFile to reference.
Setup effort
One command — npx -y @just-every/mcp-read-website-fast