ExecuteAutomation Playwright vs pwa-debug
ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). pwa-debug is a plugin bundle for AI coding tools published by aryanduntley. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ExecuteAutomation Playwright |  pwa-debug |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffcdfc3d929 Forks (GitHub): 539 Pulls (Docker Hub): 22 978 Stars (Docker Hub): 1 Stars (GitHub): 5 666 Not marked · First seen |
Not listed |
| Community marketplace aryanduntley/pwa-debug-layer | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ExecuteAutomation Playwright | pwa-debug |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 666 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 22 978 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 539 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/mcp-playwright) | On your machine (@aryanduntley/pwa-debug) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 32 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/executeautomation/mcp-playwright | github.com/aryanduntley/pwa-debug-layer |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ExecuteAutomation Playwright
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌.
pwa-debug
Browser-side debug layer that exposes live PWA state (DOM, framework state, stores, events, library popups) to AI agents via MCP. Pairs with the optional chrome-devtools-mcp (registered separately); the bundled chrome-devtools-coexistence skill walks Claude through adding it.
How to run each
ExecuteAutomation Playwright As a local MCP server: Docker image
claude mcp add --transport stdio playwright-mcp-server -- docker run -i --rm mcp/mcp-playwrightpwa-debug As a Claude Code plugin
/plugin marketplace add aryanduntley/pwa-debug-layer
/plugin install pwa-debug@pwa-debugCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of pwa-debug publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ExecuteAutomation Playwright · What it can do: pwa-debug · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.