MCP server for browser automation using Puppeteer
MCP Scrape Copilot MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. MCP server for browser automation using Puppeteer.
A Model Context Protocol server that provides browser automation capabilities using Puppeteer. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
Once MCP Scrape Copilot is connected, these are the calls the assistant has available:
puppeteer_navigate — Navigate to any URL in the browserInput — url (string)puppeteer_screenshot — Capture screenshots of the entire page or specific elementsInputs — - name (string, required): Name for the screenshotpuppeteer_click — Click elements on the pagepuppeteer_hover — Hover elements on the pagepuppeteer_fill — Fill out input fieldspuppeteer_select — Select an element with SELECT tagpuppeteer_evaluate — Execute JavaScript in the browser consoleTools — The Tools tool exposed by this serverResources — 1. Console Logs (console://logs) - Browser console output in text format - Includes all console messages from the browserThe server ships on npm as version, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of browser automation 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. MCP Scrape Copilot's toolset — puppeteer_navigate, Input, puppeteer_screenshot and 8 more — is a fair guide to whether it matches your workflow. It is maintained by jwaldor; 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.
| Tool | What it does |
|---|---|
| puppeteer_navigate | Navigate to any URL in the browser |
| Input | url (string) |
| puppeteer_screenshot | Capture screenshots of the entire page or specific elements |
| Inputs | - name (string, required): Name for the screenshot |
| puppeteer_click | Click elements on the page |
| puppeteer_hover | Hover elements on the page |
| puppeteer_fill | Fill out input fields |
| puppeteer_select | Select an element with SELECT tag |
| puppeteer_evaluate | Execute JavaScript in the browser console |
| Tools | The Tools tool exposed by this server. |
| Resources | 1. **Console Logs** (console://logs) - Browser console output in text format - Includes all console messages from the browser |
{
"mcpServers": {
"puppeteer": {
"command": "docker",
"args": ["run", "-i", "--rm", "--init", "-e", "DOCKER_CONTAINER=true", "mcp/puppeteer"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.