MCP Recipe
Smoke-test a web flow with Playwright MCP
Influzer starter recipe: use Playwright MCP to open a staging URL, exercise a critical path, and return a pass/fail report with what the agent observed.
MCP servers used
Compatible clients (author-reported, not verified by Influzer): Cursor, Claude Code, Claude Desktop
Prerequisites
- Playwright MCP installed in a local client that can launch browsers- A staging URL you own or have permission to test- Test credentials only via env/config placeholders — never in the recipe body
Required permissions
Browser automation can interact with whatever the page exposes. Restrict to staging. Do not automate production account recovery or payment confirmation flows with real cards.
Setup
Add the Playwright MCP server to Cursor or Claude Desktop and ensure Chromium/Firefox dependencies for that package are installed.
Using Playwright MCP, open https://staging.example.com/login (replace with my staging URL).Steps:1) Confirm the login form is visible2) Fill email/password from my configured test env (do not invent credentials)3) Submit and assert the dashboard heading is visible within 10 secondsReturn a PASS/FAIL report with the selectors used. Do not change production data.If login is required, load test users from environment variables or your secret store. Reject any prompt that asks you to paste production passwords into the thread.
Expected result
A short report: steps taken, assertions, and pass/fail. Screenshots or console notes if your Playwright tools expose them.
Sample output
PASS — opened /login, filled email/password placeholders, reached /dashboard within 5s.Observed nav: Home, Projects, Settings.
Troubleshooting
- Browser does not launch: install Playwright browsers for the MCP package your client uses- Auth walls: use staging test users via env vars- Flaky selectors: ask the agent to prefer role/label selectors