Ext Ops Panel
Open dashboard
Comparison

devharness vs io.github.microsoft/playwright-mcp

devharness is an MCP server published by InDate. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.microsoft/playwright-mcp is an MCP server published by microsoft. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Cursor: cursor/plugins, Docker MCP Catalog, Community GitHub marketplaces). As of our marketplace pass on 2026-11-08. 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
Marketplacedevharnessio.github.microsoft/playwright-mcp
npm registry (MCP servers) Listed
Version: 0.17.17
Downloads/month (npm): 2 360
Downloads/week (npm): 1 088
Forks (GitHub): 5
Stars (GitHub): 19
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.0.84
Downloads/month (npm): 24 354 243
Downloads/week (npm): 5 573 528
Forks (GitHub): 3 406
Stars (GitHub): 39 339
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: not stated
Forks (GitHub): 4 835
Stars (GitHub): 46 418
Not marked · First seen
Cursor: cursor/plugins Not listed Listed
Version: 1.0.0
Forks (GitHub): 1 646
Stars (GitHub): 15 712
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:8771dc4666e7
Forks (GitHub): 3 406
Pulls (Docker Hub): 2 705 524
Stars (Docker Hub): 39
Stars (GitHub): 39 339
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

devharness vs io.github.microsoft/playwright-mcp
Factdevharnessio.github.microsoft/playwright-mcp
Marketplaces that list it (differs)1 (worse)5 (better)
Stars (GitHub) (differs)19 (worse)46 418 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub2 705 524
Forks (GitHub) (differs)5 (worse)4 835 (better)
Last release (differs)2026-11-01 (better)2026-10-31 (worse)
Where it runs (differs)On your machine (devharness)On your machine (@playwright/mcp)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published23
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
LicenceMITMIT
Repository (differs)github.com/indate/devharnessgithub.com/microsoft/playwright-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-10-122026-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

devharness

In its own words, on npm registry (MCP servers):

MCP server that connects AI assistants to Chrome DevTools Protocol for runtime debugging - set breakpoints, inspect variables, monitor network traffic, and automate browser interactions

io.github.microsoft/playwright-mcp

In its own words, on Official MCP Registry:

Playwright Tools for MCP

How to run each

devharness

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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 devharness 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: devharness · What it can do: io.github.microsoft/playwright-mcp · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. 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