Puppeteer MCP reference server (archived)

Archived Puppeteer reference server for browser automation; no longer maintained. This is not Playwright.

Local (stdio)CredentialArchived upstream

Archived upstream. This server is no longer maintained by its authors and receives no fixes or security updates. The configuration below is kept for existing users; review the upstream notice before installing it. For new setups, see the maintained Playwright MCP listing.

Set up Puppeteer Automation (archived)

Configuration examples, not tested connections. Replace placeholders and review the upstream documentation before use.

Claude Code

Run in your terminal.

claude mcp add puppeteer -- npx -y @modelcontextprotocol/server-puppeteer

Cursor

Merge into ~/.cursor/mcp.json

{
  "mcpServers": {
    "puppeteer": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-puppeteer"
      ]
    }
  }
}

Codex

Run in your terminal.

codex mcp add puppeteer -- npx -y @modelcontextprotocol/server-puppeteer

Gemini CLI

Merge into ~/.gemini/settings.json

{
  "mcpServers": {
    "puppeteer": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-puppeteer"
      ]
    }
  }
}

OpenCode

Merge into ~/.config/opencode/opencode.jsonc

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "puppeteer": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@modelcontextprotocol/server-puppeteer"
      ],
      "enabled": true
    }
  }
}

VS Code

Merge into .vscode/mcp.json

{
  "servers": {
    "puppeteer": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-puppeteer"
      ]
    }
  }
}

Step-by-step setup guides: Claude Code and Codex CLI, Cursor and VS Code. In Claude Desktop, the Cursor JSON goes in claude_desktop_config.json. This is a local server that runs on your machine; see remote vs local servers and authentication and security basics.

Overview

This entry is the archived Puppeteer reference server, published as @modelcontextprotocol/server-puppeteer. Despite this listing's identifier, it is not a Playwright server. It is in the servers-archived repository, which says the archived servers are no longer maintained and come with no security guarantees.

It let an agent drive a real Chrome browser through Puppeteer. Its tools included puppeteer_navigate, puppeteer_screenshot, puppeteer_click, puppeteer_hover, puppeteer_fill, puppeteer_select and puppeteer_evaluate, which runs JavaScript in the page. It also exposed the browser console log and the screenshots it took as resources. Typical uses were checking how a page renders, walking through a simple form, or collecting console errors while debugging a front end.

Setup caveats: upstream warns that because the browser runs on your machine, the server can reach local files and local or internal IP addresses, so be careful about what an agent is allowed to open. Launch options can be changed with the PUPPETEER_LAUNCH_OPTIONS environment variable or per call. Launch arguments that reduce security, such as --no-sandbox or --disable-web-security, are refused unless allowDangerous is set, and you should leave that off. As the package is unmaintained, it will not receive fixes. We keep this page so existing users can find their configuration and its status.

Example tools

  • puppeteer_navigate
  • puppeteer_screenshot
  • puppeteer_click
  • puppeteer_fill
  • puppeteer_evaluate

Tool names are upstream examples. The server's live tool list can differ.

Browse Developer Tools servers

Sources

This page was written from the upstream documentation below and last reviewed on 11 October 2026. Listing is not a security or compatibility endorsement. Report a correction through the contact page.