Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs Website Screenshot Tool (Bulk)

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). Website Screenshot Tool (Bulk) is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 PlaywrightWebsite Screenshot Tool (Bulk)
Docker MCP Catalog Listed
Version: sha256:5ffcdfc3d929
Forks (GitHub): 540
Pulls (Docker Hub): 23 345
Stars (Docker Hub): 1
Stars (GitHub): 5 671
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
No figure published
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 Website Screenshot Tool (Bulk)
FactExecuteAutomation PlaywrightWebsite Screenshot Tool (Bulk)
Marketplaces that list it11
Stars (GitHub) (differs)5 671No figure on GitHub
Pulls (Docker Hub) (differs)23 345No figure on Docker Hub
Forks (GitHub) (differs)540No figure on GitHub
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (mcp/mcp-playwright)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)32Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/executeautomation/mcp-playwrightNot stated
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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 🔌.

Website Screenshot Tool (Bulk)

In its own words, on Official MCP Registry:

Website screenshots for every URL in a dataset, CSV or Google Sheet, desktop and mobile

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

Website Screenshot Tool (Bulk)

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

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

Only Website Screenshot Tool (Bulk) has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Website Screenshot Tool (Bulk) 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: Website Screenshot Tool (Bulk) · 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