mcp-puppeteer
If you are the rightful owner of mcp-puppeteer and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.
A simple MCP Server for controlling Chrome via Puppeteer.
This MCP server is designed to control Google Chrome using Puppeteer, a Node library that provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. The server uses `puppeteer-core`, which does not include its own browser, so users must start Chrome with the remote debugging port enabled. This setup allows for remote control of the browser, making it useful for automated testing, web scraping, and other browser automation tasks. The server communicates using Server-Sent Events (SSE), which is a protocol for streaming updates from a server to a client. This is particularly useful for real-time applications where the server needs to push updates to the client as they happen.
Features
- Uses Puppeteer for browser automation.
- Communicates via Server-Sent Events (SSE).
- Requires Chrome to be started with remote debugging enabled.
- Configurable through a JSON-based MCP server configuration.
- Supports integration with Cursor for enhanced control.
Tools
Inspector
Tools for debugging and monitoring MCP servers can be started with
pnpx @modelcontextprotocol/inspector
