Primary capability
Navigation/screenshots/forms
Documentation ↗MCP server / browser automation / source-linked
Puppeteer MCP
Legacy Puppeteer reference MCP; official repository is archived and unmaintained. The archival warning is part of the recommendation, not a footnote: a working legacy command can still lack current fixes. Use this page to plan migration and to avoid presenting old examples as maintained guidance.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Legacy Puppeteer reference MCP; official repository is archived and unmaintained. The archival warning is part of the recommendation, not a footnote: a working legacy command can still lack current fixes. Use this page to plan migration and to avoid presenting old examples as maintained guidance.
Implementation source ↗
Legacy Puppeteer reference MCP; official repository is archived and unmaintained. The archival warning is part of the recommendation, not a footnote: a working legacy command can still lack current fixes. Use this page to plan migration and to avoid presenting old examples as maintained guidance.
Implementation source ↗
Legacy Puppeteer reference MCP; official repository is archived and unmaintained. The archival warning is part of the recommendation, not a footnote: a working legacy command can still lack current fixes. Use this page to plan migration and to avoid presenting old examples as maintained guidance.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- local stdio legacy
- Authentication
- No key; local browser
Use the official endpoint/package, store secrets outside committed config, and review returned tools before use.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
npx -y @modelcontextprotocol/server-puppeteerWhat it actually exposes.
Concrete capabilities with maintainer sources.
Secondary capability
JavaScript evaluation
Documentation ↗Workflow fit
Choose by transport, auth and state needs.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Signal: selector burden
A Hacker News discussion contrasts selector-heavy Puppeteer MCP usage with browser MCPs that expose console logs and accessibility snapshots.
“The Puppeteer MCP server doesn't work well because it requires CSS selectors.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed decision workflow (proposed; not tested)
Suggested evaluation, not an observed test result.
- Choose a bounded public test task.
- Record setup, tool calls and source URLs.
- Review result, cost and failure boundaries.
What to inspect: Suggested evaluation; not tested.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
No maintenance or security fixes.
Boundary reference ↗Can reach local/internal IPs.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
Suggested evaluation; not tested.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Playwright MCP | Editorial inference: you need a different workflow. | Compare transport, auth and state tradeoffs. Documentation ↗ |
| Browserbase MCP | Editorial inference: you need another workflow. | Compare scope and operational tradeoffs. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
What should I verify first?
Confirm current endpoint, auth and returned tools.
Documentation ↗
Is this page a test result?
No; the workflow is a proposed editorial comparison.
Documentation ↗
Source trail.
Maintainer documentation used in this record.