Ext Ops Panel
Open dashboard
Comparison

ExecuteAutomation Playwright vs io.github.browserbase/mcp-server-browserbase

ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.browserbase/mcp-server-browserbase is an MCP server published by browserbase. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). 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 Playwrightio.github.browserbase/mcp-server-browserbase
Docker MCP Catalog Listed
Version: sha256:5ffcdfc3d929
Forks (GitHub): 538
Pulls (Docker Hub): 22 939
Stars (Docker Hub): 1
Stars (GitHub): 5 663
Not marked · First seen
Listed
Version: sha256:f90cb76e34ba
Pulls (Docker Hub): 38 003
Stars (Docker Hub): 1
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 2.1.1
Forks (GitHub): 373
Stars (GitHub): 3 403
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 io.github.browserbase/mcp-server-browserbase
FactExecuteAutomation Playwrightio.github.browserbase/mcp-server-browserbase
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)5 663 (better)3 403 (worse)
Pulls (Docker Hub) (differs)22 939 (worse)38 003 (better)
Forks (GitHub) (differs)538 (better)373 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-playwright)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declares (differs)326
Environment variables it asks for (differs)Not published3, secrets among them: 2
Licence (differs)MITApache-2.0
Repository (differs)github.com/executeautomation/mcp-playwrightgithub.com/browserbase/mcp-server-browserbase
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.

Tools each declares

Only ExecuteAutomation Playwright declares

  • clear_codegen_session
  • end_codegen_session
  • get_codegen_session
  • playwright_assert_response
  • playwright_click
  • playwright_click_and_switch_tab
  • playwright_close
  • playwright_console_logs
  • playwright_custom_user_agent
  • playwright_delete
  • playwright_drag
  • playwright_evaluate
Show the remaining 20
  • playwright_expect_response
  • playwright_fill
  • playwright_get
  • playwright_get_visible_html
  • playwright_get_visible_text
  • playwright_go_back
  • playwright_go_forward
  • playwright_hover
  • playwright_iframe_click
  • playwright_iframe_fill
  • playwright_navigate
  • playwright_patch
  • playwright_post
  • playwright_press_key
  • playwright_put
  • playwright_save_as_pdf
  • playwright_screenshot
  • playwright_select
  • playwright_upload_file
  • start_codegen_session

Only io.github.browserbase/mcp-server-browserbase declares

  • act
  • end
  • extract
  • navigate
  • observe
  • start

Both declare

None

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

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: io.github.browserbase/mcp-server-browserbase · 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