Fetcher MCP MCP Server

Fetcher MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for fetching web content using Playwright browser.

What you get

• fetch_url - Retrieve web page content from a specified URL
• Uses Playwright headless browser to parse JavaScript
• Supports intelligent extraction of main content and conversion to Markdown
• Supports the following parameters:
• url: The URL of the web page to fetch (required parameter)
• timeout: Page loading timeout in milliseconds, default is 30000 (30 seconds)

What the assistant can call

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

• fetch_url — Retrieve web page content from a specified URL
• url — The URL of the web page to fetch (required parameter)
• timeout — Page loading timeout in milliseconds, default is 30000 (30 seconds)
• waitUntil — Specifies when navigation is considered complete, options: 'load', 'domcontentloaded', 'networkidle', 'commit', default is 'load'
• extractContent — Whether to intelligently extract the main content, default is true
• maxLength — Maximum length of returned content (in characters), default is no limit
• returnHtml — Whether to return HTML content instead of Markdown, default is false
• waitForNavigation — Whether to wait for additional navigation after initial page load (useful for sites with anti-bot verification), default is false
• navigationTimeout — Maximum time to wait for additional navigation in milliseconds, default is 10000 (10 seconds)
• disableMedia — Whether to disable media resources (images, stylesheets, fonts, media), default is true
• debug — Whether to enable debug mode (showing browser window), overrides the --debug command line flag if specified
• fetch_urls — Batch retrieve web page content from multiple URLs in parallel

Setting it up

fetcher-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the browser automation 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. Fetcher MCP's toolset — fetch_url, url, timeout and 11 more — is a fair guide to whether it matches your workflow. It is maintained by jae-jae; 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.

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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Fetcher MCP.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the fetcher mcp mcp server does with a few real requests.