A simple MCP Server for controlling Chrome via Puppeteer

@ratiofu

リポジトリ

基本情報

カテゴリ

ブラウザ自動化

ライセンス

MIT license

トランスポート

stdio

作者

ratiofu

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 の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

A simple MCP Server for controlling Chrome via Puppeteer のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

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

よくある質問

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.

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.

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.

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.

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.

「ブラウザ自動化」の他のコンテンツ

Playwright Mcp

microsoft

Playwright MCP server

34.8K

TinyFish

tinyfish

Give your AI agent the live web. One MCP server for Search, Fetch, Browser, and Agent: browse real sites, extract structured data, fill forms, and run multi-step workflows. Search and Fetch are free.