Overview
Playwright MCP (Microsoft, 36k+ stars, Apache-2.0) is a Playwright-based MCP browser automation server supporting Chromium, Firefox, and WebKit. Chrome DevTools MCP (Chrome DevTools team, 49k+ stars, Apache-2.0) is a Puppeteer-based MCP focused on deep Chrome DevTools integration (performance tracing + network debugging). We compare browser coverage, automation engine, debugging capabilities, and typical scenarios.
TypeScript · Apache-2.0
Playwright MCP is a Microsoft MCP server exposing Playwright browser automation capabilities to AI agents, supporting web interaction, screenshots, and structured data extraction.
TypeScript · Apache-2.0
MCP server providing Chrome DevTools capabilities to coding agents, enabling web debugging, performance analysis, and DOM manipulation automation.
| Best for | Playwright MCP | Chrome DevTools MCP |
|---|---|---|
| Browser coverage | Multi-browser: Chromium, Firefox, WebKit, Microsoft Edge. Common for cross-browser testing scenarios. | Officially supports Google Chrome and Chrome for Testing only. Other Chromium browsers are not guaranteed to work. |
| Automation engine | Playwright driver. Based on structured accessibility snapshots (no pixel input), LLM-friendly. Better determinism. | Puppeteer + Chrome DevTools Frontend. Native Chrome DevTools integration (performance traces, source-mapped stack traces, CrUX field data). |
| Tool capabilities | Core automation (click, navigate, snapshot, type) + tab management + network mocking + storage + DevTools + coordinate actions + PDF generation + test assertions. Optional --caps enable vision, pdf, devtools, network capabilities. | Input automation (10 tools) + navigation (6 tools) + emulation + performance + network + debugging + memory + extensions + WebMCP + PWA. More granular official tools. |
| Installation and integration | npx @playwright/mcp@latest to start. Supports Claude Code, Cursor, VS Code, Windsurf, Claude Desktop, and other MCP clients. | npx chrome-devtools-mcp@latest to start. Supports Claude Code, Cursor, Cline, Codex, Copilot, Gemini, Grok, and other major AI clients. |
| Best fit | Cross-browser compatibility testing, E2E testing, general web automation, scenarios needing multi-browser support. | Chrome-only debugging, performance tracing, network analysis, developers needing deep DevTools data. |
| Metric | Playwright MCP | Chrome DevTools MCP |
|---|---|---|
| Stars | 36.7k | 50.6k |
| Forks | 3.1k | 3.6k |
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | Apache-2.0 |
| Last commit | September 2, 2026 | September 3, 2026 |
Choose based on your primary workflow, language ecosystem, and integration needs. Review each project's documentation and recent GitHub activity before adopting it in production.
Pick Playwright MCP for cross-browser testing; pick Chrome DevTools MCP for Chrome-only deep debugging (performance tracing, network analysis). Both integrate via MCP into AI clients.
Yes. Both projects explicitly support Claude Code, Cursor, and other major MCP clients. Claude Code adds them via the `claude mcp add` command; Cursor uses Settings.
Yes. Officially supports Google Chrome and Chrome for Testing only. Other Chromium browsers are not guaranteed. Use Playwright MCP for Firefox / WebKit.
Yes. A common combination is Playwright MCP for daily browser automation plus Chrome DevTools MCP for deep performance analysis. They complement each other.