Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs WebPerf Snippets

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). WebPerf Snippets is an MCP server published by nucliweb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
MarketplaceExecuteAutomation PlaywrightWebPerf Snippets
Docker MCP Catalog Listed
Version: sha256:5ffcdfc3d929
Forks (GitHub): 540
Pulls (Docker Hub): 23 293
Stars (Docker Hub): 1
Stars (GitHub): 5 671
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0
Forks (GitHub): 90
Stars (GitHub): 1 454
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

ExecuteAutomation Playwright vs WebPerf Snippets
FactExecuteAutomation PlaywrightWebPerf Snippets
Marketplaces that list it11
Stars (GitHub) (differs)5 671 (better)1 454 (worse)
Pulls (Docker Hub) (differs)23 293No figure on Docker Hub
Forks (GitHub) (differs)540 (better)90 (worse)
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (mcp/mcp-playwright)On your machine (webperf-snippets)
Transportstdiostdio
Tools it declares (differs)32Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/executeautomation/mcp-playwrightgithub.com/nucliweb/webperf-snippets
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-21

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

In its own words, on Docker MCP Catalog:

Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌.

WebPerf Snippets

In its own words, on Official MCP Registry:

Measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium

How to run each

ExecuteAutomation Playwright As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio playwright-mcp-server -- docker run -i --rm mcp/mcp-playwright

WebPerf Snippets As a local MCP server: npm package

Claude Code
claude mcp add --env "CRUX_API_KEY=<YOUR_CRUX_API_KEY>" --transport stdio webperf-snippets -- npx -y webperf-snippets mcp

Requires: CRUX_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of WebPerf Snippets 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: WebPerf Snippets · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built