MCP.so
ログイン

Puppeteer MCP Server

@merajmehrabi

基本情報

カテゴリ

ブラウザ自動化

ライセンス

MIT

トランスポート

stdio

作者

merajmehrabi

Puppeteer MCP Server について

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

Puppeteer MCP Server の設定

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

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

Puppeteer MCP Server のツール

8

Connect to an existing Chrome instance with remote debugging enabled

Navigate to a URL

Take a screenshot of the current page or a specific element

Click an element on the page

Fill out an input field

Select an element on the page with Select tag

Hover an element on the page

Execute JavaScript in the browser console

概要

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

よくある質問

1

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.

2

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.

3

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.

4

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.

5

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.

コメント

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