puppeteer/puppeteer

Selection

Select when

• You need a JavaScript or TypeScript API for Chrome or Firefox automation.
• You want headless browser operation by default.
• You need DevTools Protocol or WebDriver BiDi access.
• You want the main package to download a compatible Chrome build.
• You prefer puppeteer-core so browser acquisition remains under your control.
• You need CSS, ARIA, text, XPath, or piercing selectors.
• You need programmatic browser or driver installation and launching.
• You are adding Puppeteer end-to-end tests to an Angular CLI project.
• You want browser infrastructure for the separately hosted chrome-devtools-mcp server.
• You need configurable browser mirrors or private download providers.

Boundaries

Avoid when

• You require a native Claude Code plugin, skill, or hook from this repository.
• You require an MCP server bundled and implemented in this repository.
• You need WebKit coverage.
• You cannot install or provide compatible browser binaries and system dependencies.
• You require a browser manager that launches arbitrary system Firefox installations.
• You need visual judgment or human-quality UX assessment rather than browser automation.
• You cannot accept the security exposure of automating authenticated browser sessions.
• You need a fully evidenced privacy or agent-threat model from the supplied files.

Strengths

Capabilities

Risk profile

Risks and limitations

• Uncertainty: only selected first-party README files were supplied, so core implementation, package manifests, security policy, CI configuration, WebMCP details, and complete API behavior were not inspected.
• Uncertainty: repository update and push timestamps extend into 2026 relative to this analysis context, so current release status and recency cannot be independently reconciled.
• Uncertainty: Claude Code is not named in the supplied Puppeteer files; compatibility is an inference through the separately hosted chrome-devtools-mcp server and generic MCP clients.
• The chrome-devtools-mcp server is linked as a separate installation, so its implementation, permissions, host compatibility, and security behavior are outside the supplied evidence.
• The README labels WebMCP support experimental, and the supplied files do not establish Claude Code support for that path.
• Puppeteer covers Chrome and Firefox but does not document WebKit support.
• The main package depends on an install script to download Chrome, and package managers may block that script.
• Browser downloads and launches require compatible Node, archive utilities, binaries, and operating-system dependencies that vary by platform.
• The browser manager states that launching system browsers is limited to Chrome or Chromium.
• Docker guidance adds SYS_ADMIN for Chrome sandboxing or mentions disabling the sandbox, each of which requires security review.
• Automating logged-in pages can expose cookies, page content, and consequential controls to the calling program or agent.
• Custom browser providers are explicitly unsupported and leave binary compatibility, testing, and maintenance to the user.

Browser automation inherits the authority of the launched profile, pages, credentials, downloads, and network environment. The supplied Docker guidance says SYS_ADMIN enables Chrome sandboxing and alternatively mentions --no-sandbox, which weakens isolation and should not be treated as equivalent. Separately installed MCP tooling adds another trust boundary not assessed by these files.