Playwright Trace Decoder MCP server
MCP server for unpacking and analyzing Playwright trace.zip archives
1 stars49 downloads/wk
Reviews
Write oneNobody has reviewed Playwright Trace Decoder yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Playwright Trace Decoder tools (16)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
analyze_race_conditionsDetects potential race conditions by finding network requests that were still
compare_tracesCompares a passing and a failing trace of the same test. Aligns actions by sequence,
correlate_dom_and_networkJoins the HAR network log and DOM snapshots into an explicit causal chain.
detect_performance_anomaliesDetects Long Tasks and frame drops that cause Playwright timeouts. Analyses screencast-frame
extract_trace_metadata_strictStrictly inspects a Playwright trace archive and returns format version, retry session
generate_error_signatureGenerates a stable 12-char hash signature for a test failure by normalizing the
get_action_timelineReturns a paginated timeline of all actions with locators and timings. Use limit/offset to page through large traces.
get_aria_accessibility_treeReturns the ARIA accessibility tree (YAML) for a frame snapshot in the trace.
get_causal_chain_for_failureWalks backwards from the failed action and builds a chronological chain of
get_console_errorsReturns JS exceptions and warnings. Use limit/offset to page through results.
get_dom_mutation_deltaDiffs the ARIA tree before and after a specific action. Returns added and removed
get_element_state_at_failureReturns DOM attributes of the failing element at the moment of failure
get_filtered_network_logsReturns only 4xx/5xx network responses, stripping static assets. Use limit/offset to page through results.
get_screenshot_at_failureReturns the screenshot (base64 JPEG) from the trace closest to the moment of failure.
get_test_metadataReturns test metadata: title, browser, platform, viewport, and start time
get_trace_summaryReturns the failing action and top-level error message from a Playwright trace
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan14 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 129 days ago8/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Playwright Trace Decoder compares
Against every graded Scraping and browsing MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 82/100
- higher than 58% of 868 Scraping and browsing servers
- Tools
- 16
- the typical Scraping and browsing server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 50% of 581 Scraping and browsing servers
- Downloads a week
- 49
- more than 37% of 304 Scraping and browsing servers with a package
What its tools let an agent do: 15 read · 1 create
Install Playwright Trace Decoder in Claude Code, Cursor or VS Code
Runs npx -y playwright-trace-decoder-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add playwright-trace-decoder-mcp -- npx -y playwright-trace-decoder-mcp
What the publisher says
From the Playwright Trace Decoder repository's README, as published. We do not edit it. Read it on GitHub
🎭 playwright-trace-decoder-mcp
An MCP server that unpacks and structures Playwright trace.zip archives so AI agents can perform root-cause analysis on CI failures — without drowning in raw JSON or blowing up the context window.
🤔 The Problem
When a Playwright test fails in CI, you get a trace.zip. It's a binary blob. LLMs can't read it natively, and dumping the raw contents exceeds the context window. Engineers end up copying log snippets into ChatGPT manually like it's 2022.
This MCP server solves that: 16 focused tools that expose exactly the signal an agent needs to diagnose a failure, with pagination and ARIA compression to keep token costs low.
🐸 E2E Failure Investigation Example
Here is a quick look at how an AI agent uses the new tools in v0.3.0 to instantly find and inspect a failure:
- Locate the exact source code bug via maplocatorto_source:
// Request arguments
{ "trace_path": "/path/to/trace.zip" }
// Response payload
{
"action_type": "Click locator('#super-toad-not-found')",
"locator": "#super-toad-not-found",
"error": "TimeoutError: locator.click: Timeout 5000ms exceeded.",
"step_title": "Click locator('#super-toad-not-found')",
"stack": [
{
"file": "/Users/albertdev/Projects/ideas/sample-playwright-project/tests/google-pom.spec.ts",
"line": 18,
"column": 17
}
],
"source_location": {
"file": "/Users/albertdev/Projects/ideas/sample-playwright-project/tests/google-pom.spec.ts",
"line": 18,
"column": 17
}
}No more guessing! The agent knows exactly which file, line, and column caused the timeout.
- Extract critical visual frames around the failure via extractcriticalframes:
// Request arguments
{ "trace_path": "/path/to/trace.zip", "limit": 1 }
// Response payload
[
{
"timestamp": 1779137404287,
"mime_type": "image/jpeg",
"step_title": "Clicking #super-toad-not-found element",
"data": "/9j/4AAQSkZJRgABAQAAAQABAAD/..." // Base64 JPEG
}
]Allows the agent to visual-verify page state immediately before/after failure without pulling massive image lists.
- Trim the trace to save CI storage / transfer costs via trimtracearchive:
// Request arguments
{ "trace_path": "/path/to/trace.zip" }
// Response payload
{
"original_size_bytes": 2449682,
"trimmed_size_bytes": 511698,
"compression_ratio_percent": 79,
"trimmed_trace_path": "/path/to/trace.trimmed.zip"
}Shrinks large traces by deleting screenshots outside the critical failure window. Saved 79% of disk space!
🛠️ Tools
Tools are grouped by how an agent should sequence them when diagnosing a failure.
Inspection — read trace data
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Playwright Trace Decoder: common questions
- Is Playwright Trace Decoder MCP server safe?
- Mostly: it is graded B (82/100). Read the Playwright Trace Decoder safety report
- How do I install Playwright Trace Decoder?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Playwright Trace Decoder need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Playwright Trace Decoder maintained?
- The last commit was 165 days ago (2026-05-21). The latest release is v0.2.3.
- What can I use instead of Playwright Trace Decoder?
- Servers from other publishers that do the same job: Playwright MCP server, invisible_playwright_mcp MCP server and CloakBrowser MCP server.
- How does Playwright Trace Decoder compare with other Scraping and browsing MCP servers?
- safety score 82/100 (higher than 58% of 868 Scraping and browsing servers); tools 16 (the typical Scraping and browsing server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Playwright Trace Decoder
Same job from other publishers: the closest match first, then the best rated.
- PlaywrightPlaywright Tools for MCPnot reviewedWidely usedA
- invisible_playwright_mcpAI browser agent: browses, clicks, types, and reads real web pages from plain-English instructions.not reviewedEstablishedA
- CloakBrowser MCPPlaywright MCP-compatible browser automation bridge for CloakBrowser Chromium.not reviewedEstablishedB
EndformFind failing, flaky, and slow Playwright tests on Endform and keep your suite healthy as it grows.not reviewedGrowingA- Good EggsMCP server for Good Eggs grocery shopping automation using Playwright.not reviewedGrowingA