MCP server for browser automation using puppeteer-extra and puppeteer-extra-plugin-stealth
MCP server for browser automation using puppeteer-extra and puppeteer-extra-plugin-stealth. The puppeteer mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 13 defined tools rather than through you.
A Model Context Protocol server that provides enhanced browser automation capabilities using Puppeteer-Extra with Stealth Plugin. This server enables LLMs to interact with web pages in a way that better emulates human behavior and avoids detection as automation.
Everything the assistant can do here goes through one of these:
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 browserInstallation — The Installation tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at mcp/puppeteer-extra on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
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. Puppeteer's toolset — puppeteer_navigate, Input, puppeteer_screenshot and 10 more — is a fair guide to whether it matches your workflow. It is maintained by gpaul-faldin; 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.
| 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 |
| Installation | The Installation tool exposed by this server. |
| Building | The Building tool exposed by this server. |
{
"mcpServers": {
"puppeteer": {
"command": "docker",
"args": ["run", "-i", "--rm", "--init", "-e", "DOCKER_CONTAINER=true", "mcp/puppeteer-extra"]
}
}
}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.