MCP Url Fetcher MCP Server

MCP server for fetching and processing URL content in various output formats

Local serverstdio

What is the MCP Url Fetcher MCP server?

MCP Url Fetcher MCP server exists for a simple reason — assistants are far more useful when they can act on MCP Url Fetcher directly instead of describing what you should do. MCP server for fetching and processing URL content in various output formats.

What you get

A Model Context Protocol (MCP) server that fetches content from any URL and converts it to your desired output format.

MCP URL Format Converter provides tools for retrieving content from any web URL and transforming it into various formats (HTML, JSON, Markdown, or plain text), regardless of the original content type. It's designed to work with any MCP-compatible client, including Claude for Desktop, enabling LLMs to access, transform, and analyze web content in a consistent format.

  • 🔄 Format Conversion: Transform any web content to HTML, JSON, Markdown, or plain text
  • 🌐 Universal Input Support: Handle websites, APIs, raw files, and more
  • 🔍 Automatic Content Detection: Intelligently identifies source format
  • 🧰 Robust Library Support: Uses industry-standard libraries:
  • Cheerio for HTML parsing
  • Marked for Markdown processing

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once MCP Url Fetcher is connected, these are the calls the assistant has available:

  • Prerequisites — The Prerequisites tool exposed by this server
  • fetch — Fetches content from any URL and automatically detects the best output format

Configuration and credentials

  • Node.js 16.x or higher - npm or yarn

Before you rely on it

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp url fetcher mcp server does with a few real requests.

Choosing this one

Among the search and retrieval options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Url Fetcher's toolset — Prerequisites, fetch — is a fair guide to whether it matches your workflow. It is maintained by nathanonn; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
PrerequisitesThe Prerequisites tool exposed by this server.
fetchFetches content from any URL and automatically detects the best output format.

How to install the MCP Url Fetcher MCP server

{
     "mcpServers": {
       "url-converter": {
         "command": "node",
         "args": ["/absolute/path/to/mcp-url-converter/build/index.js"]
       }
     }
   }

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 16.x or higher - npm or yarn

Example prompts to try

  • Use MCP Url Fetcher to Prerequisites.
  • Use MCP Url Fetcher to fetch.

Frequently asked questions

It connects MCP Url Fetcher to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Prerequisites, fetch) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Url Fetcher directly.