Mmcp.market

Playwright Report MCP server

by hubertgajewski·io.github.hubertgajewski/playwright-report-mcp·v3.3.0

Run Playwright tests and surface structured results for AI agents doing test failure analysis.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars134 downloads/wk

Reviews

Write one

Nobody has reviewed Playwright Report yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Playwright Report tools (5, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_failed_tests

    Return failed tests from the last run with error messages and attachment paths.

  • get_run_statuswrite action

    Return status for a tracked Playwright run. Pass runId for a specific background run, or omit it to inspect the latest tracked run for a workingDirectory. If no tracked run exists, returns idle with current results.json metadata; it does not inspect unrelated OS processes.

  • get_test_attachment

    Read the content of a named attachment for a specific test from the last run.

  • list_tests

    List all tests with their spec file and tags without running them.

  • run_testswrite action

    Run Playwright tests and return structured results.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan9 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Playwright Report repository's README, as published. We do not edit it. Read it on GitHub

Playwright Report MCP

An MCP (Model Context Protocol) server for running Playwright tests and reading structured results, failed test details, and attachment content — designed for AI agents doing test failure analysis.

Table of contents

  • What it is
  • What it is NOT
  • Why
  • Quick start
  • Tools
  • Attachments
  • Installation
  • Configuration
  • Requirements
  • Troubleshooting
  • Development
  • Cutting a release

What it is

Playwright Report MCP gives an AI agent structured, token-efficient access to Playwright test outcomes. It runs your test suite, reads the JSON reporter output, and surfaces exactly what the agent needs: which tests failed, what the errors were, and the content of relevant attachments.

What it is NOT

There are many Playwright MCP servers that control a browser — they navigate pages, click elements, fill forms, and take screenshots. Playwright Report MCP is not one of those.

Why

The problem with existing approaches

Default reporters (list / dot) — Playwright's default reporters print human-readable output to stdout. Compact, but lossy: no attachment paths, no retry breakdown, no structured data.

HTML reporter (report.html) — A self-contained SPA bundle (typically 2–50 MB). Not machine-readable as text and exceeds any LLM context window.

Reading results.json directly — Works, but a full JSON report for even a small test suite is 10,000–20,000 tokens. For a failing test, most of that is passing test metadata you don't need.

What Playwright Report MCP does instead

  • Filters results.json to only failed tests
  • Returns structured, typed JSON the agent can act on immediately
  • Exposes individual attachments by name so the agent fetches only what it needs
  • Works on results produced by anyone — CI pipeline, a human, or the agent itself

Token cost comparison (one failed test in a 20-test suite)

Approximate input token counts based on Claude tokenization (~3–4 characters per token for mixed JSON/text content).

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y playwright-report-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add playwright-report-mcp -- npx -y playwright-report-mcp
Add to Cursor

Playwright Report: common questions

Is Playwright Report MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Playwright Report safety report
How do I install Playwright Report?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Playwright Report need an API key?
No secret keys are declared. It reads 2 settings from the environment.
Is Playwright Report maintained?
The last commit was in the last day (2026-09-23). The latest release is v3.3.0.
What can I use instead of Playwright Report?
Servers from other publishers that do the same job: Vibe Test — Browser Testing Agent MCP server, five46 MCP server and Clickcast MCP server. Compare all Playwright Report alternatives.

Alternatives to Playwright Report

Same job from other publishers: the closest match first, then the best rated.

All Playwright Report alternatives →
  • Vibe Test — Browser Testing Agent
    Code-aware browser testing agent — 14 Playwright tools for AI code editors via MCP
    B
  • five46
    BYOK, fully local AI agent that tests your app/API and writes a real Playwright spec on success.
    B
  • Clickcast
    Drive a real Playwright browser: annotated screenshot + structured page state after every action.
    B
  • Playrunner
    Discover Playwright workflows, start runs, and inspect results in Playrunner Cloud.
    A
  • Loadster
    Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
    A

More from hubertgajewski →