Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs Firefox DevTools MCP

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). Firefox DevTools MCP is an MCP server published by mozilla. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 PlaywrightFirefox DevTools MCP
Docker MCP Catalog Listed
Version: sha256:5ffcdfc3d929
Forks (GitHub): 539
Pulls (Docker Hub): 22 978
Stars (Docker Hub): 1
Stars (GitHub): 5 666
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.5
Downloads/month (npm): 15 837
Downloads/week (npm): 4 248
Forks (GitHub): 66
Stars (GitHub): 483
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 Firefox DevTools MCP
FactExecuteAutomation PlaywrightFirefox DevTools MCP
Marketplaces that list it11
Stars (GitHub) (differs)5 666 (better)483 (worse)
Pulls (Docker Hub) (differs)22 978No figure on Docker Hub
Forks (GitHub) (differs)539 (better)66 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-playwright)On your machine (@mozilla/firefox-devtools-mcp)
Transportstdiostdio
Tools it declares (differs)32Not published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Licence (differs)MITNot stated
Repository (differs)github.com/executeautomation/mcp-playwrightgithub.com/mozilla/firefox-devtools-mcp
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 🔌.

Firefox DevTools MCP

In its own words, on Official MCP Registry:

Control and debug Firefox: navigate, fill forms, inspect network and console, profile.

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

Firefox DevTools MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio firefox-devtools-mcp -- npx -y @mozilla/firefox-devtools-mcp --tool-preset developer

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

Tools each declares

The marketplaces of Firefox DevTools MCP 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: Firefox DevTools MCP · 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