Skip to content
All tags

#cdp

2 posts
tech deep-dive Browser Automation and MCP

Choosing a Browser MCP: CDP, Playwright MCP, or Puppeteer MCP?

It's really a two-way choice now: @playwright/mcp (cross-browser, accessibility tree, token-cheap) versus chrome-devtools-mcp (Chrome's official server, performance and memory diagnostics). @modelcontextprotocol/server-puppeteer has been archived and is no longer a candidate. The dividing line is no longer abstraction level — it's 'drive the page' versus 'diagnose Chrome'.

#mcp#browser-automation#playwright#puppeteer#cdp#ai-agent#developer-tools
tech deep-dive Browser Automation and MCP

Chrome DevTools MCP: The MCP Server Wired Directly to CDP

chrome-devtools-mcp, maintained by the Chrome team, packages DevTools capability as an MCP server: performance traces and insights, Lighthouse audits, heap snapshots, extension management — none of which @playwright/mcp exposes. It runs on Puppeteer, so interactions auto-wait; the costs are Chrome-only support and usage statistics reported to Google by default.

#chrome#cdp#mcp#browser-automation#debugging#devtools#ai-agent