ExecuteAutomation Playwright vs Oya Browser
ExecuteAutomation Playwright is an MCP server published by executeautomation. Marketplaces we read that list it: 1 (Docker MCP Catalog). Oya Browser is an MCP server published by OyadotAI. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  ExecuteAutomation Playwright |  Oya Browser |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5ffcdfc3d929 Forks (GitHub): 539 Pulls (Docker Hub): 23 047 Stars (Docker Hub): 1 Stars (GitHub): 5 666 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.195 Forks (GitHub): 279 Stars (GitHub): 353 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
| Fact | ExecuteAutomation Playwright | Oya Browser |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 5 666 (better) | 353 (worse) |
| Pulls (Docker Hub) (differs) | 23 047 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 539 (better) | 279 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/mcp-playwright) | Remote server (oyabrowser.com/mcp/pool) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 32 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/executeautomation/mcp-playwright | github.com/oyadotai/oya-browser |
| Changes in the last 7 days (differs) | 0 | 16 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌.
Oya Browser
Real Chrome for agents: start a browser, read pages as numbered markdown, click, type, hand off.
How to run each
ExecuteAutomation Playwright As a local MCP server: Docker image
claude mcp add --transport stdio playwright-mcp-server -- docker run -i --rm mcp/mcp-playwrightOya Browser As a remote MCP server
claude mcp add --transport http oya-browser https://oyabrowser.com/mcp/pool --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Oya Browser 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: Oya Browser · 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. 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.