Chrome DevTools MCP vs Playwright MCP
Two MCP servers from our browser automation ranking, compared on live data - updated nightly, never sponsored.
Bottom line · 2026-08-25
Playwright MCP records significantly more monthly package installs (25,988,876 vs 7,879,708); both are actively maintained, with commits inside the last month.
How they differ in kind
Chrome DevTools MCP focuses on: Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. Playwright MCP focuses on: A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. Tool coverage differs: Chrome DevTools MCP documents 40 tools (including click, drag, fill, fill_form); Playwright MCP documents 16 (including browser_click, browser_close, browser_console_messages, browser_drag).
What each one does
Chrome DevTools MCP
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis. Its 40 documented tools cover heapsnapshot, page, performance, take.
From the project's README.
Playwright MCP
A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models. Its 16 documented tools cover browser, navigate, network. It runs locally over stdio via the published package.
From the project's README.
14 signals, side by side
| Signal | Chrome DevTools MCP | Playwright MCP |
|---|---|---|
| Monthly installs | 7,879,708 | 25,988,876 |
| GitHub stars | 49,617 | 36,436 |
| Last commit | 2026-08-23 | 2026-08-21 |
| Releases · last 90 days | 7 | 4 |
| In the registry since | Sep 2025 | May 2026 |
| Registry versions | 49 | 8 |
| Documented tools | 40 | 16 |
| Env vars extracted | none extracted - see README | none extracted - see README |
| Runs | local (stdio) | local (stdio) |
| Endpoint auth | local only | local only |
| Maintenance | actively maintained | actively maintained |
| License | Apache-2.0 | Apache-2.0 |
| Language | TypeScript | TypeScript |
| Category rank | #2 of 196 | #1 of 196 |
What their tools cover
Extracted from each project's README - the tools each server hands your agent. A missing list means the README doesn't document one, not that no tools exist.
Chrome DevTools MCP 40 tools documented
clickdragfillfill_formhandle_dialoghoverpress_keytype_text
+32 more on the full page
Playwright MCP 16 tools documented
browser_click- Perform click on a web pagebrowser_close- Close the pagebrowser_console_messages- Returns all console messagesbrowser_drag- Perform drag and drop between two elementsbrowser_drop- Drop files or MIME-typed data onto an element, as if dragged from…browser_evaluate- Evaluate JavaScript expression on page or elementbrowser_file_upload- Upload one or multiple filesbrowser_fill_form- Fill multiple form fields
+8 more on the full page
In the wild
Public posts about Chrome DevTools MCP or Playwright MCP. Linked sources - not MCPhq reviews or ratings.
-
@simonw · · Claude Code + real browser control · Playwright MCP
“Now Claude Code can use a Chrome browser directly! Here's my TIL: Using Playwright MCP with Claude Code.”
-
@debs_obrien · · Manual QA without reading source · Playwright MCP
“Manual Testing with AI - Used Playwright MCP + a simple prompt file to test my site. no source code. Navigated to the podcast page.”
-
@debs_obrien · · One-click VS Code install · Playwright MCP
“it is super easy to install the Playwright MCP with the new VS Code settings. No CLI, No JSON, just click install.”
Which one, for what
Derived from the signals above, not hands-on testing.
Pick Chrome DevTools MCP if…
- → release velocity matters - 7 releases in 90 days vs 4
- → you want broader documented coverage - 40 tools listed vs 16
Pick Playwright MCP if…
- → you want the more widely installed option - 25,988,876 monthly installs vs 7,879,708
- → its documented toolset fits - 16 tools including browser_click, browser_close
Who's behind them
Chrome DevTools MCP - chromedevtools: 1 MCP server tracked, 1 maintained, 49,617 combined stars.
Playwright MCP - microsoft: 9 MCP servers tracked, 9 maintained, 43,350 combined stars. Full record.
Not sold on either?
The next-ranked browser automation servers we track:
Quick answers
Is Chrome DevTools MCP better than Playwright MCP?
Package installs favor Playwright MCP: 25,988,876 monthly installs to 7,879,708. Chrome DevTools MCP still ranks #2 of 196 maintained browser automation servers. Data as of 2026-08-25; we haven't hands-on tested either.
Can I use Chrome DevTools MCP and Playwright MCP together?
Yes - MCP clients accept multiple servers in one config, so you can enable both browser automation servers side by side. If their tools overlap, keep the one whose toolset fits to keep your agent's tool list lean.
Keep exploring: best browser automation servers · TypeScript servers · all comparisons · every server
Methodology: package-usage signal = npm/PyPI installs (last month, platform APIs) · maintenance = commit recency + release cadence (GitHub) · tool lists and environment-variable names extracted from each project's README · endpoint auth from our own nightly probes. We haven't hand-tested these servers; everything here is data as of 2026-08-25.