ExecuteAutomation Playwright vs mcp-browser-use
ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). mcp-browser-use is a plugin bundle for AI coding tools published by Igor Tarasenko. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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 | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffcdfc3d929 Forks (GitHub): 540 Pulls (Docker Hub): 23 960 Stars (Docker Hub): 1 Stars (GitHub): 5 681 Not marked · First seen |
Not listed |
| Community marketplace saik0s/mcp-browser-use | Not listed | Listed Version: 0.3.0 Forks (GitHub): 110 Stars (GitHub): 972 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 | mcp-browser-use |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 5 681 (better) | 972 (worse) |
| Pulls (Docker Hub) (differs) | 23 960 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 540 (better) | 110 (worse) |
| 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 (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/executeautomation/mcp-playwright | github.com/saik0s/mcp-browser-use |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-04 |
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 🔌.
mcp-browser-use
Browser automation via MCP - AI-driven web interactions with Playwright
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-playwrightmcp-browser-use As a Claude Code plugin
/plugin marketplace add saik0s/mcp-browser-use
/plugin install mcp-browser-use@browser-useCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of mcp-browser-use publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of ExecuteAutomation Playwright publish no settings it asks for, so we do not compare settings.
What it can do: ExecuteAutomation Playwright · What it can do: mcp-browser-use · 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.