ExecuteAutomation Playwright vs browser-harness
ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). browser-harness is a plugin bundle for AI coding tools published by browser-use. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffcdfc3d929 Forks (GitHub): 538 Pulls (Docker Hub): 22 939 Stars (Docker Hub): 1 Stars (GitHub): 5 664 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 1 804 Stars (GitHub): 18 403 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 | browser-harness |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 664 (worse) | 18 403 (better) |
| Pulls (Docker Hub) (differs) | 22 939 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 538 (worse) | 1 804 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/mcp-playwright) | Installs as a plugin bundle |
| 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 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/executeautomation/mcp-playwright | github.com/browser-use/browser-harness |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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 🔌.
browser-harness
Open-source browser agent driven via CDP — direct browser control, 79K stars, YC W25. browser-harness gives Claude Code direct, low-level control of a real Chrome browser via the Chrome DevTools Protocol. Coordinate-level clicks pass through iframes, shadow DOM, and cross-origin frames at the compositor level — no selector hunting, no Playwright wrappers. Connects to a long-running Browser Use Cloud or local browser session, so logins persist across runs. Highlights: - Screenshot-first workflow: capture → read pixel → click_at_xy → re-capture to verify - Bulk HTTP fetch helper for static pages (no browser overhead) - Raw CDP escape hatch for anything helpers don’t cover - Interaction skills for dialogs, dropdowns, iframes, shadow DOM, file uploads, cross-origin frames - Remote browsers via Browser Use Cloud — share a live URL with a human when login/CAPTCHA blocks the agent
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-playwrightbrowser-harness
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of browser-harness 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: browser-harness · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.