mcps
P

Recipe

Testing web apps automatically with Playwright MCP

Describe a user flow in English. Playwright MCP runs it as a real browser test, no test code required.

for Devs and QA who want a sanity check on a flow without standing up Selenium

Hand-checked recipe · curated by Ilya Gindin

15 minutes

to run

beginner

difficulty

1

connector

What you'll need

Playwright Runs the browser, executes the steps, returns logs and screenshots.
Required

This recipe runs in 4 steps

  1. 1

    Install Playwright MCP

    Say to your AI

    Add Playwright MCP to Claude Desktop — browsers are set up automatically.

    You'll get: Claude confirms Playwright is installed and a Chromium binary is available.

  2. 2

    Describe the test scenario

    Say to your AI

    Test our signup flow: go to https://myapp.com/register, fill in the form with test@example.com, click submit, and verify we see a confirmation message.

    You'll get: Claude narrates each action as it runs and reports pass/fail at each step.

  3. 3

    Watch it run

    Say to your AI

    If anything fails, dump the DOM around the failure and the network request that broke.

    You'll get: DOM snippet + the failing request/response. Claude proposes a likely cause.

  4. 4

    Screenshot proof

    Say to your AI

    Take screenshots of each step and create a test report.

    You'll get: A folder of PNGs and a Markdown report you can paste into a PR description or QA log.

You're done when

Automated browser testing without writing a single line of test code — best for one-off flow checks and regression sanity passes.

Why this workflow exists

Most regressions are caught manually because writing a real test costs more than the bug itself. Playwright MCP makes the cost negligible: describe the flow once, run it whenever you want, save the result if you want to keep it.

This isn’t a replacement for a real test suite. It’s a replacement for “let me click around real quick to make sure that still works.”