Puppeteer MCP Server

What it does

• Browser automation tools: navigate, click, hover, fill, select, evaluate, screenshot
• Console logs exposed as `console://logs` resource; screenshots as `screenshot://<name>`
• npx `@modelcontextprotocol/server-puppeteer`; PUPPETEER_LAUNCH_OPTIONS env or per-call launchOptions

When to use it

When Claude needs a real browser: scrape a JS-rendered page, drive a UI flow, take screenshots for visual verification. For heavier automation look at Playwright-based community servers.

Getting started

Add to .mcp.json under mcpServers.puppeteer:

{
  "command": "npx",
  "args": ["-y", "@modelcontextprotocol/server-puppeteer"]
}

Docker (headless chromium): `{"command": "docker", "args": ["run", "-i", "--rm", "--init", "-e", "DOCKER_CONTAINER=true", "mcp/puppeteer"]}`.

Things to know

Archived reference implementation. Real security surface: it runs a browser that can hit local files and internal IPs — README carries an explicit caution. npx mode opens a visible browser window; only the Docker image is headless.