Defuddle Fetch MCP Server

Fetch content from the web, cleaned up nicely for LLMs (using Defuddle). That is what the defuddle fetch mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A Model Context Protocol server that provides web content fetching capabilities using the Defuddle library. This server enables LLMs to retrieve and process content from web pages, automatically cleaning up the HTML and converting it to clean, readable markdown.

The MCP protocol is a standard for giving AI models access to tools.

• Better Content Extraction — Uses Defuddle to remove webpage clutter and extract main content: while keeping things like the page title and key metadata
• Flexible Output — Supports both markdown and raw HTML output
• Chunked Reading — Supports pagination with start_index and max_length parameters
• Rich Metadata — Extracts title, author, publication date, word count, and more

The tools it exposes

The server publishes 2 tools. What each one is for:

• fetch — Fetches a URL from the internet and extracts its contents as clean, markdown text using Defuddle
• Tools — The Tools tool exposed by this server

Getting it running

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.

How it compares

Among the developer tooling 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. Defuddle Fetch's toolset — fetch, Tools — is a fair guide to whether it matches your workflow. It is maintained by domdomegg; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Things to watch

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.