Test your web app in a real browser

Clicking through the same flows after every change is slow, and bugs still slip through.

3 stepsModerate

Claude CodeCursorPlaywrightGitHub

How it connects

Your AI reaches your apps through small connectors called MCP servers.

Your AI

Claude CodeCursor

Connectors

PlaywrightGitHub

Your apps

GitHub

This setup is for developers and QA engineers who re-test the same user flows after every change. The agent drives a real browser through Microsoft's Playwright MCP server, follows the flow you describe in plain language, and reports what failed. You end up with a pass or fail report per flow and GitHub issues with steps to reproduce for anything broken.

Set it up

3 steps. Open one for the details.

1Add Playwright MCP
Register the Playwright MCP server in Claude Code or Cursor with the command npx @playwright/mcp@latest. The first run may ask you to install a browser; follow the prompt or run npx playwright install. Ask the agent to open your staging URL and describe the page to confirm it works.
Tip: Add the --headless flag if you do not need to watch the browser.
2Describe the flow
Describe the flow step by step in plain language: the URL, the test account, what to click or type, and what a correct result looks like. The agent reads the page through accessibility snapshots, so clear button labels and form field names help it find the right elements. Ask it to report each step as passed or failed, with the error text or a screenshot when something breaks.
Tip: Write the expected result for each step, otherwise the agent has to guess what "working" means.
3File what fails
Connect GitHub's MCP server with permission to create issues in your repository. Ask the agent to open one issue per failure with the steps to reproduce, the expected and actual result, the browser used and any console errors. Review each issue before approving the create call.
Tip: Ask the agent to turn a flow that keeps breaking into a Playwright test file you can run in CI.

Then just ask

Things to say once it's connected. Click one to copy it.

Ask Claude Code…Claude Code

Good to know

What you need, what it won't do, and how to keep it safe.

What you need

Node.js installed locally
Claude Code or Cursor
Staging environment and test accounts
GitHub repository access to create issues

Limits

The agent can misread complex or poorly labelled pages and click the wrong element.
Exploratory runs are slower and less repeatable than a scripted test suite.
CAPTCHAs, two-factor prompts and email verification steps usually need a manual workaround.

Keep it safe

Run against staging, not production.
Use test accounts, never real customer credentials.

Playwright MCP Server (browser-control) GitHub MCP Server (repository-read, issue-write, pull-request-write)

Questions

Straight answers before you start

Does this replace my Playwright test suite?

No. The agent explores flows from plain-language instructions, which helps for quick checks and new features. For checks that must run on every commit, ask it to write a Playwright test file and run it in CI.

Which browsers can it use?

Playwright MCP runs Chromium by default and can be configured to use Firefox, WebKit or an installed Chrome or Edge. Pick the browser in the server's command-line options.

Is it safe to point at production?

Run it against staging with test accounts. The agent really clicks buttons and submits forms, so on production it could place orders or send emails.

Does it cost anything?

Playwright and its MCP server are free and open source. You pay only for your AI host usage, such as Claude Code or Cursor.

Tools in this setup

The products involved

GitHub

GitHub is where most software teams keep their code, review pull requests and track issues. Actions runs your CI and deployments, Projects handles planning and Copilot adds AI coding help. It connects to Slack, Linear and Jira. Public and private repositories are free, with paid plans for larger teams and security features.

Free planTry