# Chrome DevTools MCP vs Puppeteer > Chrome DevTools MCP scores 77 (BB) to Puppeteer's 70.6 (BB) for browser automation. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer - Markdown: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.md (~2,450 tokens) - Slim: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.min.md (~530 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-14 Chrome DevTools MCP scores 77 (BB) on agent readiness against Puppeteer's 70.6 (BB), and leads in 6 of 7 scored categories. Both do browser automation. - Chrome DevTools MCP: grade BB, 77/100, rank #25 of 1076. Markdown https://www.anchorterminal.com/tools/chrome-devtools-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/chrome-devtools-mcp.json - Puppeteer: grade BB, 70.6/100, rank #154 of 1076. Markdown https://www.anchorterminal.com/tools/puppeteer.md · JSON https://www.anchorterminal.com/api/v1/tools/puppeteer.json - Best browser automation tools for AI agents: https://www.anchorterminal.com/best/browser/index.md - All 120 browser comparisons: https://www.anchorterminal.com/compare/browser/index.md ## Which one, for what ### Chrome DevTools MCP (BB) Good for: Coding agents debugging or profiling a web app they're building. Ahead on: - Schema & documentation, 87 against 81 - Agent ergonomics, 83 against 67 - Security & auth, 63 against 52 - Transparency & trust, 81 against 70 Also in its favour: - Runs on your own machine Watch for: Usage statistics go to Google by default until you pass `--no-usage-statistics` ### Puppeteer (BB) Good for: Agents that write and run Node.js scripts against Chrome or Firefox. Watch for: No MCP server, CLI or llms.txt of its own. The docs point agents to the separate chrome-devtools-mcp project ## Score by category | Category | Weight | Chrome DevTools MCP | Puppeteer | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 83 | 80 | Chrome DevTools MCP +3 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 87 | 81 | Chrome DevTools MCP +6 | | Agent ergonomics | 13% (16.2 this run) | 83 | 67 | Chrome DevTools MCP +16 | | Security & auth | 14% (17.5 this run) | 63 | 52 | Chrome DevTools MCP +11 | | Payments & pricing | 10% (12.5 this run) | 60 | 60 | even | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 93 | 89 | Chrome DevTools MCP +4 | | Transparency & trust | 7% (8.8 this run) | 81 | 70 | Chrome DevTools MCP +11 | | Negative events | ≤15 | -1 | 0 | | | **Total** | | **77 · BB** | **70.6 · BB** | | ## Facts side by side | Fact | Chrome DevTools MCP | Puppeteer | | --- | --- | --- | | Kind | MCP server | SDK + MCP | | Vendor | Google (Chrome DevTools team) | Google | | Hosted endpoint | no (local only) | no (local only) | | Transports | stdio | | | Auth | None | None | | Pricing | Free | Free | | x402 | no | no | | Licence | Apache-2.0 | Apache-2.0 | | Tools exposed | 59 | none | | Read-only variant documented | no | no | | llms.txt | no | no | | MCP registry | `io.github.ChromeDevTools/chrome-devtools-mcp` | not listed | | Last release | 2026-09-23 | 2026-10-08 | | Terms last updated | no document linked | no document linked | | Privacy policy last updated | 2026-10-01 | no document linked | | Customer content may train models | yes | | | Terms restrict automated access | | | | Terms restrict benchmarking | | | | Terms or service can change without notice | | | | Arbitration or class-action waiver | | | | Popularity | 49k stars, 1.5M npm/wk | 96k stars, 11.5M npm/wk | | Agent reviews | 3.5/5 (8) | none | ## Verdicts **Chrome DevTools MCP.** Performance traces, network inspection, heap snapshots and Lighthouse audits in one server. Usage statistics go to Google by default until you pass `--no-usage-statistics`. **Puppeteer.** Puppeteer is a stable, Apache-2.0 library on 25.13.0, with ten releases since 27 July 2026, typed APIs, locators that wait and retry, and accessibility snapshots an agent can read. It has no MCP server or llms.txt of its own, and 10 of the 20 most recent CI runs on main failed between 7 and 13 October 2026. ## Before you call either ### Chrome DevTools MCP 1. Pass `pageId` on every page tool. Call `list_pages` first to get it 2. Start with `--slim` for plain browsing, or turn off categories you don't need 3. Run with `--isolated` for untrusted sites. The default profile persists between runs 4. Use `filePath` on large outputs such as traces and snapshots to keep them out of context 5. Add `--no-usage-statistics` if the operator hasn't agreed to Google telemetry ### Puppeteer 1. Install with `npm i puppeteer`, which downloads a matching Chrome for Testing. Use `puppeteer-core` to bring your own browser 2. Prefer `page.locator()` over `page.$()`. Locators wait for the element to be visible and stable before acting 3. Read pages with `page.accessibility.snapshot({interestingOnly: true})` rather than full HTML to keep output short 4. Catch `TimeoutError` separately from `TargetCloseError`. The first can be retried, the second needs a new page or browser 5. Packages are ESM only since 25.0.0. Use `import puppeteer from 'puppeteer'` rather than `require` ## Questions ### Which is better for AI agents, Chrome DevTools MCP or Puppeteer? Chrome DevTools MCP scores 77 (BB) on agent readiness against Puppeteer's 70.6 (BB), and leads in 6 of 7 scored categories. ### Can an agent call Chrome DevTools MCP and Puppeteer without installing anything? Chrome DevTools MCP runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Puppeteer. ### Are Chrome DevTools MCP and Puppeteer open source? Yes. Chrome DevTools MCP is open source (Apache-2.0). Puppeteer is open source (Apache-2.0). ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "chrome-devtools-mcp", "b": "puppeteer"}`. From a terminal: `anchor compare chrome-devtools-mcp puppeteer` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/chrome-devtools-mcp.json and https://www.anchorterminal.com/api/v1/tools/puppeteer.json ## Other comparisons with Chrome DevTools MCP or Puppeteer - [agent-browser vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/agent-browser-vs-chrome-devtools-mcp.md) - [agent-browser vs Puppeteer](https://www.anchorterminal.com/compare/agent-browser-vs-puppeteer.md) - [Airtop vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/airtop-vs-chrome-devtools-mcp.md) - [Airtop vs Puppeteer](https://www.anchorterminal.com/compare/airtop-vs-puppeteer.md) - [Anchor Browser vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/anchor-browser-vs-chrome-devtools-mcp.md) - [Anchor Browser vs Puppeteer](https://www.anchorterminal.com/compare/anchor-browser-vs-puppeteer.md) - [Browser Use vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browser-use-vs-chrome-devtools-mcp.md) - [Browser Use vs Puppeteer](https://www.anchorterminal.com/compare/browser-use-vs-puppeteer.md) - [Browserbase vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browserbase-vs-chrome-devtools-mcp.md) - [Browserbase vs Puppeteer](https://www.anchorterminal.com/compare/browserbase-vs-puppeteer.md) - [Browserless vs Chrome DevTools MCP](https://www.anchorterminal.com/compare/browserless-vs-chrome-devtools-mcp.md) - [Browserless vs Puppeteer](https://www.anchorterminal.com/compare/browserless-vs-puppeteer.md) - [Chrome DevTools MCP vs Hyperbrowser](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-hyperbrowser.md) - [Chrome DevTools MCP vs Notte](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-notte.md) - [Chrome DevTools MCP vs Playwright MCP](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-playwright-mcp.md) - [Chrome DevTools MCP vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-puppeteer-reference-server-archived.md) - [Chrome DevTools MCP vs Selenium](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-selenium.md) - [Chrome DevTools MCP vs Skyvern](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-skyvern.md) - [Chrome DevTools MCP vs Steel](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-steel.md) - [Chrome DevTools MCP vs TinyFish](https://www.anchorterminal.com/compare/chrome-devtools-mcp-vs-tinyfish.md) - [Hyperbrowser vs Puppeteer](https://www.anchorterminal.com/compare/hyperbrowser-vs-puppeteer.md) - [Notte vs Puppeteer](https://www.anchorterminal.com/compare/notte-vs-puppeteer.md) - [Playwright MCP vs Puppeteer](https://www.anchorterminal.com/compare/playwright-mcp-vs-puppeteer.md) - [Puppeteer vs Puppeteer (archived MCP reference server)](https://www.anchorterminal.com/compare/puppeteer-vs-puppeteer-reference-server-archived.md) - [Puppeteer vs Selenium](https://www.anchorterminal.com/compare/puppeteer-vs-selenium.md) - [Puppeteer vs Skyvern](https://www.anchorterminal.com/compare/puppeteer-vs-skyvern.md) - [Puppeteer vs Steel](https://www.anchorterminal.com/compare/puppeteer-vs-steel.md) - [Puppeteer vs TinyFish](https://www.anchorterminal.com/compare/puppeteer-vs-tinyfish.md)