How can I configure Puppeteer server options?
Use either the `PUPPETEER_LAUNCH_OPTIONS` environment variable with JSON-encoded launch settings, or pass `launchOptions` and `allowDangerous` parameters directly to the `puppeteer_navigate` tool.
@jatidevelopments
Basic information
Advanced Puppeteer automation server with enhanced functionality (MCP Server)
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"MCP-Puppeteer-Advanced-Cursor-...-": {
"command": "docker",
"args": [
"build",
"-t",
"mcp/puppeteer",
"-f",
"Dockerfile",
"."
]
}
}
}Navigate to any URL in the browser
Capture screenshots of the entire page or specific elements
Click elements on the page
Hover elements on the page
Fill out input fields
Select an element with SELECT tag
Execute JavaScript in the browser console
Extract all images from the page (both `<img>` tags and CSS background images)
Download extracted images to a specified folder
Analyze a DOM element to extract its HTML structure, Markdown representation, and applied styles
Check browser status, list open tabs, and manage tab switching
Analyze the DOM hierarchy of a page and determine parent-child relationships between elements
Switch the browser viewport to simulate different devices (mobile, tablet, desktop)
Navigate back or forward in browser history
Puppeteer is a Model Context Protocol server that provides browser automation capabilities using Puppeteer. It enables LLMs to interact with web pages, take screenshots, extract and download images, and execute JavaScript in a real browser environment.
Configure the server in your MCP client using either Docker (docker run -i --rm --init -e DOCKER_CONTAINER=true mcp/puppeteer) or NPX (npx -y @modelcontextprotocol/server-puppeteer). Optionally set PUPPETEER_LAUNCH_OPTIONS environment variable or pass launchOptions to puppeteer_navigate to customize browser behavior.
<img> tags and CSS backgroundsUse either the `PUPPETEER_LAUNCH_OPTIONS` environment variable with JSON-encoded launch settings, or pass `launchOptions` and `allowDangerous` parameters directly to the `puppeteer_navigate` tool.
The Docker implementation uses headless Chromium, while the NPX version opens a visible browser window.
Console logs at `console://logs` (browser console output in text format) and screenshots at `screenshot://<name>` (PNG images of captured screenshots).
The `allowDangerous` parameter (default false) controls whether dangerous Puppeteer launch options like `--no-sandbox` and `--disable-web-security` are permitted; setting it to true allows these options.
A flexible HTTP fetching Model Context Protocol server.
BitBrowser MCP simple to use, no complicated procedures required. Supports a variety of intelligent agent services.

An MCP server for generating images from HTML & CSS or screenshots of URLs using htmlcsstoimage.com.
This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.
An MCP server for fetching URLs / Youtube video transcript.
Comments