PWA Debug Layer vs Strata
A side-by-side look at the PWA Debug Layer and Strata MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose PWA Debug Layer for browser automation work as a local process; choose Strata 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 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.
Choose Strata when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
browser_close, browser_resize, browser_console_messages.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 5,822 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 27 | 25 |
| Full listing | View PWA Debug Layer | View Strata |
Tools & capabilities
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
Strata tools 25
browser_closeClose the pagebrowser_resizeResize the browser windowbrowser_console_messagesReturns all console messagesbrowser_handle_dialogHandle a dialogbrowser_emulate_mediaEmulate CSS media features for the page, for example switch between the light and dark color scheme. Omitted parameters are left unchanged; null clears an override.browser_evaluateEvaluate JavaScript expression on page or elementbrowser_file_uploadUpload one or multiple filesbrowser_dropDrop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.browser_findSearch the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.browser_fill_formFill multiple form fieldsbrowser_press_keyPress a key on the keyboardbrowser_typeType text into editable element- +13 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.
PWA Debug Layer
{
"mcpServers": {
"pwa-debug-layer": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Strata
{
"mcpServers": {
"strata": {
"command": "npx",
"args": [
"-y",
"@playwright/mcp@latest"
]
}
}
}
Frequently asked questions
PWA Debug Layer is categorized under Browser Automation and uses a local stdio subprocess. Strata belongs to Browser Automation and uses a local stdio subprocess. Pick PWA Debug Layer for browser automation work and Strata 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.
PWA Debug Layer has no declared pricing — check the project's own site. Strata 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 pwa-debug-layer and strata as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, PWA Debug Layer has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Strata has 65/100 (Great) with 1 views, 0 installs and 5,822 GitHub stars.
