playwright-aqa vs Vibe Test — Browser Testing Agent
playwright-aqa is a plugin bundle for AI coding tools published by MStroievus. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Vibe Test — Browser Testing Agent is an MCP server published by AishwaryShrivastav. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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 |  playwright-aqa |  Vibe Test — Browser Testing Agent |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: f5800d5 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.6 Downloads/month (npm): 1 240 Downloads/week (npm): 100 Forks (GitHub): 0 Stars (GitHub): 17 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 | playwright-aqa | Vibe Test — Browser Testing Agent |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 17 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (vibe-testing) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/mstroievus/playwright-aqa-plugin | github.com/aishwaryshrivastav/vibe-testing |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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-aqa
A Playwright + TypeScript QA automation skill that helps Claude Code write production-grade end-to-end (UI) and API tests following industry best practices. Guides Claude through Page Object Model architecture, custom per-page fixtures, robust locator and waiting strategies, APIRequestContext-based API test builders, and playwright.config.ts setup. The skill activates automatically whenever the user asks about writing, refactoring, or debugging Playwright tests — even when Playwright is not mentioned explicitly (e.g. "write an E2E test for login", "my test is flaky", "how do I test this endpoint").
Vibe Test — Browser Testing Agent
Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
How to run each
playwright-aqa As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install playwright-aqa@claude-communityVibe Test — Browser Testing Agent As a local MCP server: npm package
claude mcp add --transport stdio vibe-testing -- npx -y vibe-testingCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: playwright-aqa · What it can do: Vibe Test — Browser Testing Agent · 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 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.