Fetcher MCP for VS Code: Setup & Config

What you can do with Fetcher in VS Code

Pick it for browser-rendered content extraction with parallel fetching and practical debugging controls.

• Read content from JavaScript-rendered web pages.
• Fetch several research URLs in parallel.

Before you start: Fetcher in VS Code

• Node.js and npx
• Playwright Chromium
• An MCP-compatible client

The README first installs the browser with npx playwright install chromium. The browser_install tool can also resolve missing-browser errors. An HTTP launch alternative exposes /mcp and /sse. No required environment variables are stated.

Fetcher VS Code configuration

1. Choose VS Code configuration scope

   For Fetcher MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

2. Add Fetcher MCP to VS Code

   Use the fetcher-mcp entry below in servers. Keep Fetcher MCP's documented stdio connection fields and your other VS Code entries.

3. Check Fetcher MCP in VS Code

   Fetcher MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

{
  "servers": {
    "fetcher-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "fetcher-mcp"
      ],
      "env": {}
    }
  }
}

Fetcher tools available to VS Code

Fetcher's stored tool list documents 3 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

fetch_url

Look for fetch_url among VS Code's agent-mode tools after starting Fetcher through the MCP controls.

fetch_urls

Look for fetch_urls among VS Code's agent-mode tools after starting Fetcher through the MCP controls.

Retrieve several URLs concurrently with the same content and loading controls.

browser_install

Look for browser_install among VS Code's agent-mode tools after starting Fetcher through the MCP controls.

Install Chromium for Playwright, with optional system dependencies or forced reinstallation.

Fetcher: full stored tool descriptions

Troubleshooting Fetcher in VS Code

• Make npx fetcher-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting Fetcher MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
• Fetcher MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Needs a Playwright Chromium binary and associated runtime dependencies.
• Known limitation: Verification-heavy pages may require manual interaction or timeout tuning.
• Known limitation: Default resource blocking changes what the browser loads.
• General VS Code troubleshooting lives in the /clients/vscode guide.

Frequently asked questions