fetch_html
Fetch a website and return the content as HTML
LABSCO SUMMARY
The conversion happens before the page reaches the model, not after.
One decision separates the four tools: how much of the page you are willing to pay for. fetch_txt drops the markup entirely, fetch_markdown keeps headings and links, fetch_html keeps all of it. Custom headers are the only other control — there is no rendering step and no selector parameter, so what comes back is what the URL returns.
What it is
A fetching server with 4 tools that differ in output format, each taking a url and optional headers.
What you get
- fetch_html for the raw markup, when the structure of the page is the thing you need
- fetch_markdown for a converted version that reads in a conversation, and fetch_txt for the text with the HTML dropped
- fetch_json for a JSON file at a URL, parsed rather than handed over as text
- Headers on every call, for a page behind a user-agent check or a bearer token
Requirements
Nothing to supply — no account, no key; only a URL the machine can reach. MIT licensed.
Setup effort
One command — npx -y @tokenizin/mcp-npx-fetch
USE CASES
01
Reading an article into a conversation cheaply
Take the text when only the words matter, and the Markdown when the headings and links carry part of the meaning — both are a fraction of the raw page.
02
Pulling structured data straight off an endpoint
Take the JSON where an API answers with it, adding the headers the endpoint expects, and fall back to the raw HTML when the data is in the page rather than behind an API.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fetch_json
Fetch a JSON file from a URL
fetch_markdown
Fetch a website and return the content as Markdown
fetch_txt
Fetch a website, return the content as plain text (no HTML)
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-npx-fetch": {
"command": "npx",
"args": [
"-y",
"@tokenizin/mcp-npx-fetch"
]
}
}
}npx
TERMINAL
npx -y @tokenizin/mcp-npx-fetch
