MCP Node Fetch MCP Server

MCP Node Fetch MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. An MCP server for fetching URLs using undici.

What you get

An MCP server that enables fetching web content using the Node.js undici library.

• Fetch content from any URL using various HTTP methods
• Support for headers and request body
• Return content in various formats (text, JSON, binary, HTML fragments)
• Handle errors gracefully
• Configure timeout and redirect behavior

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.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by mcollina; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

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 node fetch mcp server does with a few real requests.