Chrome DevTools MCP vs Puppeteer

Drives a live Chrome instance over the DevTools protocol: performance traces, network requests, console output, and accessibility snapshots. It answers the question an agent normally cannot — why is this page slow — without a human exporting a profile. Best…

MCP Servers Verified 9 Nov
Install npx -y chrome-devtools-mcp@latest npx -y @modelcontextprotocol/server-puppeteer
Source Official Official
Deciding factor A developer is debugging a specific page state and… versus: The task is scheduled and repeatable, and needs a…
Bottom line

DevTools inspects the page in front of you; Puppeteer drives a browser you control.

The short answer

Both are browser automation, at different levels. The Chrome DevTools MCP inspects and interacts with a live browser session — useful for debugging a page a person is looking at. Puppeteer launches its own browser and scripts it, which is what a repeatable job needs. The distinction matters because one is a debugging aid and the other is a robot.

Facts

Option Install Source
Chrome DevTools MCP npx -y chrome-devtools-mcp@latest Repository ↗ Official
Puppeteer npx -y @modelcontextprotocol/server-puppeteer Repository ↗ Official

Pick Chrome DevTools MCP if

A developer is debugging a specific page state and wants the agent to read the console and network tab.

Pick Puppeteer if

The task is scheduled and repeatable, and needs a fresh browser session every run.

What would change our mind

A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.

Read the full entries

More head-to-heads

All comparisons