Chrome Devtools MCP vs PWA Debug Layer
A side-by-side look at the Chrome Devtools MCP and PWA Debug Layer MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Chrome Devtools MCP for browser automation work as a local process; choose PWA Debug Layer for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Chrome Devtools MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
click, drag, fill.
Choose PWA Debug Layer when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
host_status, host_list_registrations, session_ping.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 65/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 54,008 | 0 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 56 | 27 |
| Full listing | View Chrome Devtools MCP | View PWA Debug Layer |
Tools & capabilities
Chrome Devtools MCP tools 56
clickdragfillfill_formhandle_dialoghoverpress_keytype_textupload_fileclick_atclose_pagelist_pages- +44 more on the listing page
PWA Debug Layer tools 27
host_statusInstall/liveness state: registered IDs, manifest paths, launcher path, active connections. Cheap, idempotent. **Always call first.host_list_registrationsRead registered IDs; destructive cleanup to re-bootstrap.session_pingFull MCP → IPC → NMH → SW → page-world round-trip with typed `pageWorldError` codes + self-heal.pdl_check_setupDiagnose setup → `{ ok, gaps[], recommendations[] }` (CDP reachable, manifest installed, extension present, ID registered).pdl_browser_statusManaged launches (browser, profile mode, port, pid) with live debug-port re-probe + extension SW heartbeat.console_tailCursor-paginated, filterable tails of the persistent capture ring buffers (memory + disk spill).recent_eventsRecent captured events across kinds for quick verification.evaluateEvaluate an expression in the page world.session_recordrrweb session recording + cursor-paginated replay.source_map_resolveResolve generated stack frames to original `src/…:line:col`.settings_list_schemaRead the typed settings schema; get/set values (allowlist, capture filters, disk-spill, etc.).sw_statusService-worker registrations: installing/waiting/active versions, `updateViaCache`, controller, and whether an update is stuck **waiting** (the #1 "why isn't my update showing").- +15 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Chrome Devtools MCP
{
"mcpServers": {
"chrome-devtools-mcp": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp"
]
}
}
}
PWA Debug Layer
{
"mcpServers": {
"pwa-debug-layer": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Frequently asked questions
Chrome Devtools MCP is categorized under Browser Automation and uses a local stdio subprocess. PWA Debug Layer belongs to Browser Automation and uses a local stdio subprocess. Pick Chrome Devtools MCP for browser automation work and PWA Debug Layer for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Chrome Devtools MCP is listed as free. Auth: no auth required. PWA Debug Layer has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add chrome-devtools-mcp and pwa-debug-layer as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Chrome Devtools MCP has a quality signal of 65/100 (Great) with 6 views, 0 installs and 54,008 GitHub stars. PWA Debug Layer has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.
