MCP server for browser automation via Puppeteer
If you already use Pptr MCP, the pptr mcp mcp server is the piece that lets your assistant work with it directly. MCP server for browser automation via Puppeteer.
MCP server for browser automation via Puppeteer. Unlike other browser MCPs that expose fixed tools (navigate, click, screenshot), this server executes arbitrary JavaScript code with direct access to the Puppeteer Browser instance.
The server ships on npm as pptr-mcp, 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.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Multi — tenant or shared server deploymentsVariable — DescriptionCHROME_PATH — Path to Chrome executablePUPPETEER_EXECUTABLE_PATH — Alternative to CHROME_PATHPUPPETEER_CACHE_DIR — Browser download cache directoryPPTR_MCP_TIMEOUT — Execution timeout in ms (default: 30000)code — stringpersistent — booleanParameters — The Parameters tool exposed by this serverConfiguration is passed through the environment: CHROME_PATH, PUPPETEER_EXECUTABLE_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
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. Pptr MCP's toolset — Multi, Variable, CHROME_PATH and 6 more — is a fair guide to whether it matches your workflow. It is maintained by iatsiuk; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Pptr MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Multi | tenant or shared server deployments |
| Variable | Description |
| CHROME_PATH | Path to Chrome executable |
| PUPPETEER_EXECUTABLE_PATH | Alternative to CHROME_PATH |
| PUPPETEER_CACHE_DIR | Browser download cache directory |
| PPTR_MCP_TIMEOUT | Execution timeout in ms (default: 30000) |
| code | string |
| persistent | boolean |
| Parameters | The Parameters tool exposed by this server. |
With CLI options:
```json
{
"mcpServers": {
"puppeteer": {
"command": "npx",
"args": ["pptr-mcp", "--no-headless", "--viewport=1080p"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CHROME_PATH | Filesystem location the server is allowed to use. | Optional |
| PUPPETEER_EXECUTABLE_PATH | Filesystem location the server is allowed to use. | Optional |
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.