Playwright E2E MCP server

playwright-e2e-mcp

An MCP server that diagnoses and fixes failing Playwright tests. It is the layer that sits next to a browser-driving MCP: Playwright MCP gives an agent hands in the browser; this server gives it a test runner, a failure analyst and a verified fixer.

run-test ──▶ get-failure ──▶ suggest-fix (apply + re-run) ──▶ green
   │              │                 └─ refuses when the element is really gone (app bug)
   │              └─ DOM at failure, failed requests, console errors
   └─ background runs, progress ──▶ analyze-history (flaky / broken / regressed)

What it does that a browser-driving MCP or a raw npx playwright test does not:

dead dev server, syntax error, crash, full disk…) and a concrete fix hint. Long suites run in the background with live progress.

• Structured runs. Stats plus each failure's file:line, kind (assertion, timeout,

4xx/5xx requests and console errors, read from Playwright's own trace.

• Diagnosis from the trace. The DOM at the moment of failure, the failed action, the

DOM at failure, swaps in a Playwright locator proven unique on the page (getByRole('button', { name: 'Proceed to checkout' })), re-runs the test and reverts the edit if it is still red. When nothing on the page plausibly matches, it says the element is missing and does not patch the test to hide a real bug.

• Fixes that are proven, not guessed. suggest-fix matches a broken locator against the

tests that flip (flaky) from ones that started failing (regressed) or always fail (broken), and groups failures that share one cause.

• Flakiness across runs. Every run is recorded locally; analyze-history separates

headers, and click/fill steps to reach a modal or a later step.

• Pages behind a login. Every page tool accepts a Playwright storageState, extra

drifted locator cost about 5,300 tokens here against about 7,400 with Playwright MCP plus a shell, and the fix was applied and verified without the agent editing anything.

• Small on the wire. In the benchmark, diagnosing and fixing one

What it does not do

It does not drive an exploratory browsing session step by step, and it does not replace Playwright's own Test Agents (planner, generator, healer) inside VS Code. Use Playwright MCP for interactive browsing and this server for running, diagnosing and fixing the suite; they work side by side in the same client.

Demo

Hosted endpoint — what an initialize + tools/list round-trip against https://playwright-e2e-mcp.vercel.app/api/mcp returns for a client that sends the bearer token (without one, only list-tests and get-failure are listed):

A real test run — run-test served over stdio by npx -y playwright-e2e-mcp against the bundled examples/sample-test.spec.ts (actual output, unedited):

Images are rendered with node scripts/gen-demo-images.mjs: the run-test card is real captured output; the endpoint card is an illustration of the authenticated listing.

Install

Shortened. The full README is on GitHub.