Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs shaft-skills

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). shaft-skills is a plugin bundle for AI coding tools published by ShaftHQ. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-09. 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 Playwrightshaft-skills
Docker MCP Catalog Listed
Version: sha256:5ffcdfc3d929
Forks (GitHub): 540
Pulls (Docker Hub): 23 866
Stars (Docker Hub): 1
Stars (GitHub): 5 679
Not marked · First seen
Not listed
Community marketplace shafthq/shaft_engine Not listed Listed
Version: not stated
Forks (GitHub): 155
Stars (GitHub): 418
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 shaft-skills
FactExecuteAutomation Playwrightshaft-skills
Marketplaces that list it11
Stars (GitHub) (differs)5 679 (better)418 (worse)
Pulls (Docker Hub) (differs)23 866No figure on Docker Hub
Forks (GitHub) (differs)540 (better)155 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-playwright)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)32Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle37
LicenceMITMIT
Repository (differs)github.com/executeautomation/mcp-playwrightgithub.com/shafthq/shaft_engine
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-14

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

shaft-skills

In its own words, on Community GitHub marketplaces:

Official SHAFT agent skills: methodology router, locator strategy, test planning and authoring, MCP-driven recording, failure analysis, and change verification.

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

shaft-skills As a Claude Code plugin

Claude Code
/plugin marketplace add shafthq/shaft_engine
/plugin install shaft-skills@shafthq

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

Tools each declares

The marketplaces of shaft-skills 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: shaft-skills · 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.

Where the data comes from: how the catalog is built