🎭 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:

1. Locate the exact source code bug via map_locator_to_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.

2. Extract critical visual frames around the failure via extract_critical_frames:

   // 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.

3. Trim the trace to save CI storage / transfer costs via trim_trace_archive:

   // 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

... View full README on GitHub