Fetch URL MCP Server

If you already use Fetch URL, the fetch url mcp server is the piece that lets your assistant work with it directly. Intelligent web content fetcher MCP server that converts HTML to clean, AI-readable Markdown.

What the server does

An MCP server that fetches web pages and converts them to clean, readable Markdown.

This server takes a URL, fetches the page, and strips away everything you don't need — navigation, sidebars, banners, scripts — leaving just the main content as Markdown. It's perfect for feeding into LLMs, giving them the distilled essence of a page without the noise. It also recognizes GitHub, GitLab, Bitbucket, and Gist URLs and rewrites them to fetch the raw content directly.

• HTML to Markdown — — Turns any public web page into clean, readable Markdown with metadata like title, url, contentSize, and truncated
• Smart URL handling — — Recognizes GitHub, GitLab, Bitbucket, and Gist page URLs and rewrites them to raw-content endpoints before fetching
• Self-documenting — — Includes an internal://instructions resource and a get-help prompt so clients know how to use it
• HTTP mode — — Optionally serves over Streamable HTTP with host/origin validation, bearer or OAuth auth, rate limiting, health checks, and TLS

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Tools — The Tools tool exposed by this server
• Resources — The Resources tool exposed by this server
• Prompts — The Prompts tool exposed by this server

Credentials and setup notes

Configuration is passed through the environment: OAUTH_ISSUER_URL, OAUTH_AUTHORIZATION_URL, OAUTH_TOKEN_URL, OAUTH_REVOCATION_URL, OAUTH_REGISTRATION_URL, OAUTH_INTROSPECTION_URL, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET. 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.

• Node.js >= 24 - Docker (optional) — only needed if you want to run the container image

Installation

The server ships on npm as args, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

This sits in the search and retrieval group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Fetch URL's toolset — Tools, Resources, Prompts — is a fair guide to whether it matches your workflow. It is maintained by j0hanz; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Fetch URL's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.