Ext Ops Panel
Open dashboard
Comparison

Casely vs io.github.microsoft/playwright-mcp

Casely is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑26.

Casely is a plugin bundle for AI coding tools published by John Wayne. No marketplace we read lists it any more. 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-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCaselyio.github.microsoft/playwright-mcp
Community marketplace johnwayneeee/casely-qa-skill Removed on 2026-10-26
Version: 2.4.0
Forks (GitHub): 0
Stars (GitHub): 11
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 321
Stars (GitHub): 38 672
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 321
Pulls (Docker Hub): 2 563 871
Stars (Docker Hub): 38
Stars (GitHub): 38 672
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

Casely vs io.github.microsoft/playwright-mcp
FactCaselyno longer listed · io.github.microsoft/playwright-mcp
Marketplaces that list it (differs)04
Stars (GitHub) (differs)1144 708
Pulls (Docker Hub) (differs)No figure on Docker Hub2 563 871
Forks (GitHub) (differs)04 673
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.atlassian.com/v2/mcp)On your machine (@playwright/mcp)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published23
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)41
LicenceMITMIT
Repository (differs)github.com/johnwayneeee/casely-qa-skillgithub.com/microsoft/playwright-mcp
Changes in the last 7 days (differs)80
First seen (differs)2026-10-232026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of Casely

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • paranoid-qa

    English skills: evidence-disciplined testing framework, Playwright test review, test cases, Jira bug reports

    by Aleksei Kovalev · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Testiny Test Management

    Create and manage test cases, test runs and results in Testiny from your AI assistant.

    by testiny.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • testdino

    Use TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.

    by TestDino · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • qa-expert

    QA process setup with AAA test cases, P0-P4 bug tracking, metrics reports, OWASP security testing and third-party handoffs. Use for test planning, approved-batch execution and…

    by daymade · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • Qase Test Management

    Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.

    by qase.io · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • getlark

    Natural-language end-to-end tests for any software surface, powered by getlark.ai

    by getlark · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

Casely

In its own words, on Community GitHub marketplaces:

Attach requirements or name a Jira issue, add an example of your team's test cases, approve one plan, get a TestRail-ready Excel or CSV file back, plus a runnable Postman collection when the spec describes an API, and bug reports from a trace ID.

io.github.microsoft/playwright-mcp

In its own words, on Official MCP Registry:

Playwright Tools for MCP

How to run each

Casely

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

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