MCP server

Puppeteer MCP Server: Browser Control for AI Agents

This Puppeteer MCP server lets an AI agent open pages, click, fill forms and take screenshots, either in a fresh browser or in a Chrome window you already have open.

Run
npx -y puppeteer-mcp-server
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Puppeteer MCP server?

The Puppeteer MCP server by merajmehrabi gives an AI agent eight tools for browser automation with Puppeteer: navigate, screenshot, click, fill, select, hover, evaluate JavaScript and connect to an open Chrome tab. You run it with npx -y puppeteer-mcp-server. The README calls it experimental.

It is a Model Context Protocol server that wraps Puppeteer so an AI agent can control a browser. The README describes it as an experimental implementation inspired by the reference Puppeteer server in the modelcontextprotocol servers repo, with its own approach to connecting to browsers.

By default it launches a new browser instance. Its distinguishing feature is active tab mode: start Chrome with remote debugging on, and the agent can attach to a tab you already have open without closing your browser.

What it changes in your workflow

  • The agent can load a page, click a selector, fill an input and screenshot the result, so it checks its own front end changes.
  • Active tab mode lets it work in a page where you are already signed in, because it connects to your running Chrome.
  • puppeteer_evaluate runs JavaScript in the page, which helps with reading values the page computes.
  • Each call returns success or failure with an error message, and everything is also written to log files.

How it runs

Puppeteer MCP server
Where it runsOn your machine, as a Node process the client starts
Transportstdio
Installnpx -y puppeteer-mcp-server, or npm install -g puppeteer-mcp-server
BrowserPuppeteer's browser, or your own Chrome with remote debugging on port 9222
Account or keyNone

Who it is for

Best for

  • Developers who already know Puppeteer and want selector-based control from an agent.
  • Quick checks inside an existing Chrome session, such as a page behind a login you completed yourself.
  • Small scripts where eight simple tools are enough.

Not for

  • Cross-browser testing. The README describes Puppeteer and Chrome only, so use Chrome DevTools MCP or a Playwright based server for other needs.
  • Heavily maintained tooling. The repo's last push was in March 2025, and the README labels the project experimental.
  • Reading pages by structure. There is no snapshot tool; the agent targets CSS selectors you or it supply.

Use it with UiChemy

Use the server to preview a page you built with UiChemy. Composer and Figma to WordPress produce pages in Elementor or Gutenberg; the agent can open the live URL, click through the layout and capture screenshots. Click Get Started on uichemy.com to try the WordPress side.