Puppeteer MCP Server (community)

Add to your client

Copy the config for your MCP client and paste it into its config file.

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

Before you start

• Node.js 18+ (run via npx or a global install)
• Chrome/Chromium — bundled by Puppeteer for new instances; for attach mode, an existing Chrome started with `--remote-debugging-port=9222`
• No API key or authentication required (local stdio server)

About Puppeteer MCP Server (community)

Tools & capabilities (8)

When to use it

• Use it when you want the agent to operate inside your already-open, logged-in Chrome session rather than a fresh profile
• Use it when you need simple, lightweight browser automation without managing a cloud service
• Use it when you want to navigate, click, and fill forms on a page from an LLM
• Use it when you need screenshots for visual checks or scraping
• Use it when you want to run custom JavaScript against a live page to extract data
• Use it when you want a local, no-auth alternative to the reference Puppeteer MCP server

Quick setup

1. 1Ensure Node.js 18+ is installed
2. 2Add the server to your MCP client config with command `npx puppeteer-mcp-server` (stdio), or install globally with `npm install -g puppeteer-mcp-server`
3. 3For attach mode, start Chrome with `--remote-debugging-port=9222` before connecting
4. 4Restart the MCP client to load the server
5. 5Call puppeteer_connect_active_tab to attach, or puppeteer_navigate to launch a new instance
6. 6Verify by navigating to a URL and taking a screenshot

Puppeteer MCP Server (community) FAQ