MCP Puppeteer is a lightweight MCP server that allows remote control of Chrome browsers through Puppeteer, facilitating browser automation tasks efficiently.
Added on:
Created by:
Apr 22 2025
Featured
What is MCP Puppeteer?
MCP Puppeteer enables users to control Chrome browsers remotely using the MCP (Model Context Protocol) framework via Puppeteer, a popular automation library. It requires starting Chrome with remote debugging enabled and running the MCP server. Users can then connect to the server via configured clients to perform browser automation, testing, and scripting tasks. This setup streamlines browser control, making it ideal for testing, scraping, and automation workflows with easy integration into existing systems.
Who will use MCP Puppeteer?
- Developers
- Testers
- Automation Engineers
- Web Scrapers
- Quality Assurance Teams
How to use the MCP Puppeteer?
- Step1: Start Chrome with remote debugging enabled using `--remote-debugging-port=9222`
- Step2: Install dependencies with `pnpm i`
- Step3: Run the MCP server with `pnpm run start`
- Step4: Configure your MCP client to connect via the URL `http://localhost:7742/sse`
- Step5: Use the client to send commands and control the browser remotely
MCP Puppeteer's Core Features & Benefits
The Core Features
- Control Chrome via Puppeteer
- Remote browser automation
- Support for MCP protocol
The Benefits
- Enables remote browser control
- Facilitates automation and testing
- Simple setup for integrating with existing workflows
MCP Puppeteer's Main Use Cases & Applications
- Browser automation for testing and QA
- Web scraping and data extraction
- Automated browsing workflows
- Remote browser management in CI/CD pipelines