Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs android-emulator-qa-plugin

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). android-emulator-qa-plugin is a plugin bundle for AI coding tools published by ceabarr. 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

Where each is published
MarketplaceExecuteAutomation Playwrightandroid-emulator-qa-plugin
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: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
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 android-emulator-qa-plugin
FactExecuteAutomation Playwrightandroid-emulator-qa-plugin
Marketplaces that list it11
Stars (GitHub) (differs)5 664 (better)0 (worse)
Pulls (Docker Hub) (differs)22 939No figure on Docker Hub
Forks (GitHub) (differs)538 (better)0 (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 bundle2
Licence (differs)MITApache-2.0
Repository (differs)github.com/executeautomation/mcp-playwrightgithub.com/ceabarr/claude-android-plugin
Changes in the last 7 days00
First seen2026-10-112026-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

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

android-emulator-qa-plugin

In its own words, on Claude Code: claude-plugins-community:

Claude Android QA Plugin helps Claude Code test Android apps in an emulator. It can launch apps, inspect UI trees, derive safe tap coordinates, capture screenshots, and collect logcat evidence for QA and bug reproduction.

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

android-emulator-qa-plugin

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 android-emulator-qa-plugin 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: android-emulator-qa-plugin · 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.

Where the data comes from: how the catalog is built