Ext Ops Panel
Open dashboard
Comparison

playwright-pro vs io.github.microsoft/playwright-mcp

playwright-pro is a plugin bundle for AI coding tools published by alirezarezvani. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.microsoft/playwright-mcp is an MCP server published by microsoft. Marketplaces we read that list it: 4 (Official MCP Registry, Claude Code: claude-plugins-official, Cursor: cursor/plugins, Docker MCP Catalog). As of our marketplace pass on 2026-10-26. 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
Marketplaceplaywright-proio.github.microsoft/playwright-mcp
Claude Code: claude-plugins-community Listed
Version: 2.9.0
Forks (GitHub): 3 987
Stars (GitHub): 28 744
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.0.82
Downloads/month (npm): 31 345 222
Downloads/week (npm): 6 403 349
Forks (GitHub): 3 315
Stars (GitHub): 38 619
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 673
Stars (GitHub): 44 708
Not marked · First seen
Cursor: cursor/plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 421
Stars (GitHub): 14 172
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8771dc4666e7
Forks (GitHub): 3 315
Pulls (Docker Hub): 2 561 615
Stars (Docker Hub): 38
Stars (GitHub): 38 619
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

playwright-pro vs io.github.microsoft/playwright-mcp
Factplaywright-proio.github.microsoft/playwright-mcp
Marketplaces that list it (differs)1 (worse)4 (better)
Stars (GitHub) (differs)28 744 (worse)44 708 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub2 561 615
Forks (GitHub) (differs)3 987 (worse)4 673 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@playwright/mcp)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published23
Environment variables it asks for (differs)5, secrets among them: 2Not published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)171
LicenceMITMIT
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/microsoft/playwright-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

playwright-pro

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

Playwright Pro turns your AI coding agent into a senior test automation engineer. Instead of generating tutorial-quality tests with brittle CSS selectors, Playwright Pro enforces battle-tested patterns from production test suites: role-based locators, web-first assertions, proper fixture architecture, and isolated test design. It doesn't reinvent Claude Code — it orchestrates it. /pw:generate uses the built-in Explore subagent for codebase analysis. /pw:migrate delegates to /batch for parallel file conversion. /pw:fix leverages /debug for trace inspection. Every skill builds on what Claude Code already does well. 55 ready-to-use test templates across 11 categories — authentication, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API testing, and accessibility. Each template includes TypeScript and JavaScript variants with parametrizable placeholders. Not generic stubs — real patterns like Stripe iframe handling, GraphQL mutation testing, and RBAC permission flows. 3 specialized

io.github.microsoft/playwright-mcp

In its own words, on Official MCP Registry:

Playwright Tools for MCP

How to run each

playwright-pro As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install playwright-pro@claude-community

io.github.microsoft/playwright-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio playwright-mcp -- npx -y @playwright/mcp

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

Tools each declares

The marketplaces of playwright-pro publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.microsoft/playwright-mcp publish no settings it asks for, so we do not compare settings.

What it can do: playwright-pro · What it can do: io.github.microsoft/playwright-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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