DeepYard

Chrome DevTools MCP vs Playwright MCP

Side-by-side comparison built from DeepYard's structured catalog. Content updated Aug 21, 2026.

Direct Answer

Chrome DevTools MCP suits teams needing open-source access, performance profiling focus, and 49,556 GitHub stars in current listing data. Playwright MCP suits teams needing open-source access, web scraping focus, and 36,346 GitHub stars in current listing data. This summary reflects catalog metadata only for decision support, not independent testing.

What this comparison weighs

  • Pricing and free-tier availability
  • License model and deployment fit
  • GitHub adoption and contributor depth
  • Catalog tags, integrations, and supported workflows
C

Chrome DevTools MCP

Official Google MCP server giving coding agents full Chrome DevTools access — 28K+ stars

OSSFree
49.6Ktoday118
P

Playwright MCP

Browser automation and web testing via the Model Context Protocol

OSSFree
36.3K42.0K/wtoday70
MetricChrome DevTools MCPPlaywright MCP
GitHub Stars49.6K36.3K
Contributors11870
Last CommitAug 21, 2026Aug 21, 2026
Open Issues903
Licenseopen-sourceopen-source
Pricingopen-sourceopen-source
Free TierYesYes
Categorymcp-serversmcp-servers
TrendingNoNo

Choose Chrome DevTools MCP if you need

  • Chrome DevTools MCP is the stronger pick when Performance Profiling matters because that capability is listed only on its profile.
  • Chrome DevTools MCP shows broader GitHub adoption with 49,556 stars versus 36,346 for Playwright MCP.
  • Chrome DevTools MCP has a larger visible contributor base (118 vs 70).

Choose Playwright MCP if you need

  • Playwright MCP is the stronger pick when Web Scraping matters because that capability is listed only on its profile.
  • Playwright MCP is the cleaner fit if you specifically need Browser Automation workflows from the catalog tags.

Meaningful differences

  • GitHub adoption: Chrome DevTools MCP shows 49,556 stars versus 36,346 for Playwright MCP.
  • Contributor count: Chrome DevTools MCP lists 118 contributors and Playwright MCP lists 70.

Shared capabilities

  • Browser Automation

Shared Tags

No shared tags

Only in Chrome DevTools MCP

chromedevtoolsdebuggingbrowsergoogleperformanceautomation

Only in Playwright MCP

browser-automationplaywrightweb-testinge2escrapingmicrosoft

Limitations and evidence

  • DeepYard compares structured public metadata; this is not an independent benchmark unless a test record is shown.
  • Signals such as stars, contributors, and last commit indicate public activity, not purchase fit or runtime quality.
  • Pricing and feature coverage reflect the stored listing snapshot and may lag vendor changes between refreshes.

About Chrome DevTools MCP

An official Google MCP server that gives AI coding agents full access to Chrome DevTools. Enables performance trace recording with actionable insights, advanced debugging (network requests, screenshots, console messages with source-mapped stack traces), and reliable Puppeteer-based browser automation with automatic result waiting. Supports headless mode for servers, isolated mode with temp user data, and WebSocket connection to existing Chrome instances.

View full listing

About Playwright MCP

Playwright MCP is Microsoft's official MCP server that exposes Playwright's full browser automation capabilities to AI coding assistants. It enables Claude Code, Cursor, and other MCP clients to navigate web pages, click elements, fill forms, take screenshots, extract page content, and run end-to-end tests — all via natural language instructions. Built on the battle-tested Playwright engine that powers CI pipelines across the industry.

View full listing