fetchmcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fetchmcp Fetch https://en.wikipedia.org/wiki/Markdown and convert to clean Markdown"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fetchmcp
A drop-in replacement for the official fetch MCP that actually works on modern web pages.
The official fetch MCP is broken on JavaScript-heavy pages, truncates output at 5,000 characters, and ships an unpatched SSRF vulnerability. fetchmcp returns clean, LLM-ready Markdown from any URL — rendering JavaScript when needed, passing basic bot protection without paid proxies, and telling you honestly when a page is blocked instead of hallucinating content. npx and go.

// Replace the official fetch server with this — one line in your MCP config:
"fetchmcp": { "command": "npx", "args": ["-y", "@labtoolsstudio/fetchmcp"] }
Why switch
official |
| |
JavaScript pages | ❌ empty / broken | ✅ auto-renders in a real browser |
Output length | ✂️ truncated at 5,000 chars | ✅ full page, with paging |
Bot protection (403 / Cloudflare) | ❌ fails silently | ✅ passes mid-tier walls, no paid proxy |
Blocked page | ❌ returns the CAPTCHA as "content" | ✅ honest typed error, never fakes it |
SSRF safety | ❌ CVE-2025-65513 (CVSS 9.3) | ✅ private/metadata IPs refused by default |
Cost | free | free, self-hosted, |
Related MCP server: skrape
Install
Add to your MCP client config (claude_desktop_config.json, Cursor mcp.json, Cline, etc.):
{
"mcpServers": {
"fetchmcp": {
"command": "npx",
"args": ["-y", "@labtoolsstudio/fetchmcp"]
}
}
}The install is light — no browser is downloaded up front, and static reading (fetch → Readability → Markdown) works immediately. The first time a page actually needs JavaScript, fetchmcp downloads a stealth Chromium once (~150 MB) automatically, then renders it — still zero-config. To pre-download it at install time, set FETCHMCP_PREINSTALL_BROWSER=1. To stay static-only and never download it, set FETCHMCP_SKIP_BROWSER_DOWNLOAD=1 (JS pages then return an honest needs_js).
Tools
read_url
Fetch any web page as clean Markdown.
arg | type | description |
| string | the URL to fetch (http/https) |
| boolean | JS rendering: |
| boolean | return raw HTML instead of Markdown |
| object | extra request headers, e.g. |
| integer | cap characters returned ( |
| integer | offset for paging through a long page |
read_docs
Same engine, tuned for documentation: strips navigation sidebars, headers, and footers so API docs and guides come back as clean reference text. Takes url, render, headers, max_length, start_index.
Honest statuses
fetchmcp never returns a bot wall, an error page, or a truncated shell dressed up as real content. When it can't read a page it says why, with a typed status: blocked (bot protection, with the vendor), blocked_ssrf, needs_js, http_error, timeout, network_error, unsupported_content, or empty.
Configuration (env vars)
var | default | meaning |
|
| per-request timeout |
|
| retries on network errors / |
| unset | set to |
| unset | self-hosted FlareSolverr endpoint for tougher challenges |
| unset | set to |
| unset | set to |
Development & testing
npm install # installs deps (Chromium downloads on first JS use)
npm run build # compile TypeScript to dist/
npm test # unit tests (block detection, SSRF) — no network
npm run test:e2e # live end-to-end suite against real sites
# Poke at any tool/URL by hand — no need to write a script:
node test/probe.mjs read_url https://example.com
node test/probe.mjs read_url https://some-spa.example.com --render
node test/probe.mjs read_docs https://docs.python.org/3/library/json.html
node test/probe.mjs read_url https://api.example.com --header "Authorization=Bearer x" --max-length 500
node test/probe.mjs read_url https://example.com --full # print the whole responsetest/probe.mjs --help semantics are documented at the top of that file.
How it works
Three tiers, escalating only as needed:
Static — plain fetch → Readability → Markdown. Fast path for most pages.
Browser — lazy patchright (stealth Chromium) when the static HTML is an empty SPA shell, a bot wall, or a
403/429/503.FlareSolverr (optional) — only if you've configured an endpoint, for challenges the browser can't clear.
Star history
If fetchmcp saved you from one more fetch-returns-nothing moment, a star helps others find it.
License
MIT — see LICENSE.
Available Tools
2 toolsread_docsRead Documentation Page as MarkdownA
Fetch a documentation or reference page and return only its main content as clean Markdown, stripping navigation sidebars, headers, footers, and other page chrome. Use this for API docs, guides, and reference pages. For general web pages use read_url. Same JS-rendering, anti-bot, and honest-error behavior as read_url.
Inputs: url (required), render, headers, max_length, +1 more.
read_urlRead URL as MarkdownA
Fetch a web page and return its content as clean, LLM-ready Markdown. Full content by default (no truncation). Handles HTML, plain text, Markdown, and JSON responses. JavaScript-heavy pages are rendered automatically in a real browser when the static HTML is an empty SPA shell. Returns an honest typed error when the site blocks access or the content cannot be read — it never silently returns partial or fake content.
Inputs: url (required), raw, render, headers, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: read_url fetches any web page as full content, while read_docs is specifically for documentation pages and strips chrome. The descriptions explicitly call out when to use each, eliminating ambiguity.
Both tools follow the same verb_noun pattern (read_url, read_docs), making the naming predictable and intuitive. No mixed conventions or vague verbs.
With only 2 tools, the server feels slightly thin, but the narrow purpose (fetching and converting web content) justifies such a small surface. It borders on the low end of the ideal range but is not egregiously insufficient.
The tool set covers the core needs of fetching and reading web content comprehensively: general pages, documentation pages, and handling of multiple formats including JS-rendered content. No obvious missing operations for the stated purpose.
Maintenance
Related MCP Connectors
Converts any URL to clean, LLM-ready Markdown using real Chrome browsers
Fetch any URL and get clean Markdown. Web scraping for AI agents.
Web scraping for AI agents. Converts URLs to clean, LLM-ready Markdown with anti-bot bypass.
Turn web pages into clean Markdown text for LLMs and RAG. Respects robots.txt.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceFetches web pages and converts them to markdown for LLM consumption, supporting chunked reading and raw content extraction.MIT
- AlicenseNot gradedqualityDmaintenanceConverts any webpage into clean, LLM-ready Markdown, removing noise and supporting JavaScript rendering.MIT
- AlicenseNot gradedqualityDmaintenanceConverts URLs into clean, LLM-ready markdown, respecting robots.txt and never bypassing anti-bot measures or paywalls.MIT
- AlicenseNot gradedqualityCmaintenanceEnables fetching web pages as clean Markdown with automatic escalation from direct requests to residential proxies and headless browsers to overcome blocks, plus built-in politeness handling like robots.txt and rate limiting.-