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-09-30

Playwright MCP records significantly more monthly package installs (26,860,286 vs 8,032,302); 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.

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.

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 README documents 10 tools, including browser_click, browser_close, browser_console_messages.

From the project's README.

14 signals, side by side

Signal Chrome DevTools MCP Playwright MCP
Monthly installs 8,032,302 26,860,286
GitHub stars 52,777 37,711
Last commit 2026-09-30 2026-09-28
Releases · last 90 days 7 6
In the registry since Sep 2025 May 2026
Registry versions 52 11
Documented tools not extracted - see README 10
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 290 #1 of 290

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 no tool list in README

Playwright MCP 10 tools documented

  • browser_click - Perform click on a web page
  • browser_close - Close the page
  • browser_console_messages - Returns all console messages
  • browser_drag - Perform drag and drop between two elements
  • browser_drop - Drop files or MIME-typed data onto an element, as if dragged from…
  • browser_emulate_media - Emulate CSS media features for the page, for example switch between…
  • browser_evaluate - Evaluate JavaScript expression on page or element
  • browser_file_upload - Upload one or multiple files

+2 more on the full page

In the wild

Public posts about Chrome DevTools MCP or Playwright MCP. Linked sources - not MCPhq reviews or ratings.

Which one, for what

Derived from the signals above, not hands-on testing.

Pick Chrome DevTools MCP if…

  • → category standing - #2 of 290 maintained browser automation servers

Pick Playwright MCP if…

  • → you want the more widely installed option - 26,860,286 monthly installs vs 8,032,302
  • → its documented toolset fits - 10 tools including browser_click, browser_close

Who's behind them

Chrome DevTools MCP - chromedevtools: 1 MCP server tracked, 1 maintained, 52,777 combined stars.

Playwright MCP - microsoft: 9 MCP servers tracked, 9 maintained, 44,911 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: 26,860,286 monthly installs to 8,032,302. Chrome DevTools MCP still ranks #2 of 290 maintained browser automation servers. Data as of 2026-09-30; 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-09-30.