Advertise
MCP.so
Sign In

A simple MCP Server for controlling Chrome via Puppeteer

@ratiofu

Repository

Basic information

Category

Browser Automation

License

MIT license

Transports

stdio

Author

ratiofu

About A simple MCP Server for controlling Chrome via Puppeteer

A simple MCP server for controlling Chrome via Puppeteer

A simple MCP Server for controlling Chrome via Puppeteer config

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

{
  "mcpServers": {
    "puppeteer-control": {
      "type": "http",
      "url": "http://localhost:7742/sse"
    }
  }
}

A simple MCP Server for controlling Chrome via Puppeteer tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is A simple MCP Server for controlling Chrome via Puppeteer?

This MCP server connects to a running Chrome instance through its remote debugging port using Puppeteer Core. It acts as a bridge between MCP clients (like Cursor) and Chrome, allowing programmatic control via the Model Context Protocol.

How to use A simple MCP Server for controlling Chrome via Puppeteer?

First, start Chrome with the remote debugging port enabled (e.g., --remote-debugging-port=9222). Then install dependencies with pnpm i and run the server with pnpm run start. Finally, configure Cursor to add a global MCP server pointing to http://localhost:7742/sse.

Key features of A simple MCP Server for controlling Chrome via Puppeteer

  • Uses puppeteer-core (no bundled browser)
  • Requires an existing Chrome with remote debugging enabled
  • Communicates via SSE transport (not Streamable HTTP)
  • Designed for use with Cursor IDE

Use cases of A simple MCP Server for controlling Chrome via Puppeteer

  • Automating browser actions from an MCP‑compatible client
  • Integrating Chrome control into Cursor workflows
  • Experimenting with Puppeteer through MCP tools

Frequently asked questions

1

How do I start Chrome for this server?

On macOS, run `open -a "Google Chrome" --args --remote-debugging-port=9222`. The server expects Chrome to be launched manually with the debugging port.

2

What dependencies are required?

The project uses `puppeteer-core` and does not install a browser. You need Node.js, pnpm, and a Chrome/Chromium installation.

3

How do I connect this server to Cursor?

In Cursor’s MCP settings, add a new global MCP server with the URL `http://localhost:7742/sse`. The server must be running locally.

4

Why does the server use SSE instead of Streamable HTTP?

The README explains that Cursor requires SSE support. The TypeScript SDK’s Streamable HTTP example is not compatible; SSE is better documented in the official MCP documentation.

5

Can I test the server without Cursor?

Yes, you can use the MCP Inspector. With the server already running on SSE, run `pnpx @modelcontextprotocol/inspector` to explore available tools.

Comments

More Browser Automation MCP servers

Parse

Parse.bot

Parse allows your agent to access thousands of APIs instantly. You can use Parse to build an API for any action on any website and edit any previously existing API in our catalogue.

Apify Model Context Protocol (MCP) Server

apify

The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.

1.7K

Gologin MCP Server

gologinapp

MCP server for managing Gologin browser profiles, proxies, fingerprints and cloud browser sessions through AI conversations

21

Full Self Browsing

Lakshman Turlapati

DOM-first AI browser automation for Chrome and MCP clients.

194

Screenshot Scout

screenshotscout

Capture screenshots of webpages as images or PDFs with Screenshot Scout.

Advertise