Docs Fetch MCP Server

If you already use Docs Fetch MCP, the docs fetch mcp mcp server is the piece that lets your assistant work with it directly. MCP server for fetching web page content with recursive exploration capability.

What the server does

A Bun-based Model Context Protocol (MCP) server for fetching documentation pages and bounded documentation crawls.

• Fast static fetch path with axios
• Optional Puppeteer rendering for client-rendered or thin pages
• Markdown extraction with headings, lists, code blocks, tables, blockquotes, and links
• Real crawl depth semantics:
• depth: 1 returns only the root page
• depth: 2 includes direct child links

Installation

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.

Available tools

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

• depth — 1 returns only the root page
• sameOrigin — true rejects links whose origin differs from the normalized root URL
• includeLinks — false hides links in returned page objects but does not disable link discovery for crawling
• render — "never" uses only the HTTP fetch path
• url — string
• maxPages — number
• maxConcurrency — number
• timeoutMs — number
• perPageTimeoutMs — number
• pathPrefix — string
• contentLimit — number
• fetch_doc_content — The fetch_doc_content tool exposed by this server

Credentials and setup notes

• Bun >=1.3.0 - Puppeteer's browser installation if render is auto or always This project uses Bun for dependency management, runtime execution, builds, and tests.

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.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Docs Fetch MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

This sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Docs Fetch MCP's toolset — depth, sameOrigin, includeLinks and 9 more — is a fair guide to whether it matches your workflow. It is maintained by wolfyy970; worth a glance at recent repository activity before you build anything load-bearing on it.

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