MCP.so
Sign In

Puppeteer MCP Server

@merajmehrabi

About Puppeteer MCP Server

This MCP server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows.

Basic information

Category

Browser Automation

License

MIT

Runtime

node

Transports

stdio

Publisher

merajmehrabi

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "puppeteer-mcp-server": {
      "command": "npx",
      "args": [
        "puppeteer-mcp-server"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Puppeteer MCP Server?

Puppeteer MCP Server provides browser automation capabilities through Puppeteer, allowing interaction with both new browser instances and existing Chrome windows. It is designed for developers using AI assistants like Claude to automate web tasks.

How to use Puppeteer MCP Server?

Install globally via npm (npm install -g puppeteer-mcp-server) or run directly with npx puppeteer-mcp-server. Configure it as an MCP server in Claude Desktop or Claude VSCode Extension settings. Use tools such as puppeteer_navigate, puppeteer_screenshot, puppeteer_click, puppeteer_fill, puppeteer_select, puppeteer_hover, puppeteer_evaluate, and puppeteer_connect_active_tab to control the browser.

Key features of Puppeteer MCP Server

  • Navigate web pages and take screenshots
  • Click elements, fill forms, select options, hover
  • Execute JavaScript in the browser console
  • Connect to existing Chrome windows with remote debugging
  • Smart tab management that preserves existing Chrome instances
  • Detailed logging with Winston (daily rotation, 20MB max, 14 day retention)

Use cases of Puppeteer MCP Server

  • Automated web scraping and data extraction
  • UI testing and capturing screenshots for verification
  • Form filling and submission automation
  • Monitoring and interacting with dynamic web pages

FAQ from Puppeteer MCP Server

Can Puppeteer MCP Server connect to an already open Chrome window?

Yes, use Active Tab Mode: launch Chrome with --remote-debugging-port=9222, then call the puppeteer_connect_active_tab tool to connect to a specific tab or the default non-extension tab.

What tools does Puppeteer MCP Server provide?

It includes puppeteer_navigate, puppeteer_screenshot, puppeteer_click, puppeteer_fill, puppeteer_select, puppeteer_hover, puppeteer_evaluate, and puppeteer_connect_active_tab. Each tool has required and optional parameters documented in the README.

How do I configure the server with Claude Desktop?

Add a "puppeteer" entry under "mcpServers" in your claude_desktop_config.json. The command depends on installation method: use "puppeteer-mcp-server", "npx" with args ["-y", "puppeteer-mcp-server"], or "node" with the path to the built index file.

What security precautions are recommended when using remote debugging?

Only enable remote debugging on trusted networks, use a unique debugging port, close it when not in use, and never expose the port to public networks.

Where are logs stored and how are they managed?

Logs are stored in a logs/ directory with daily rotation, maximum file size of 20MB, retention of 14 days, and automatic compression of old logs. Logging levels include DEBUG, INFO, WARN, and ERROR.

Comments

More Browser Automation MCP servers