If you've tried "AI clicks the screen" automation, you know the flaky part is usually the vision step. Playwright's MCP server takes a different route: it feeds the model the page's accessibility tree, not a screenshot.
Why this matters
- Deterministic: every interactive element gets a stable ref, so the agent targets "this button" instead of guessing from pixels.
- Token-efficient: a snapshot is ~200-400 tokens vs thousands for a DOM dump or screenshot.
- No vision model required.
Install (Claude Code)
claude mcp add playwright npx @playwright/mcp@latest
It registers at user scope, runs as a local stdio subprocess, and uses headed Chromium by default. Claude Desktop, Cursor, VS Code and Windsurf work too.
Where it shines
Repetitive form flows, data extraction, and E2E/regression tests you can describe in plain language. Keep browser_snapshot as the default and reach for browser_screenshot only when you need a visual check.
Limits
It drives a real local browser, and elements outside the accessibility tree (canvas, custom widgets) are harder. Keep a human in the loop for anything sensitive.
Tags: ai, webdev, programming, testing
Disclosure: I publish Pointchecknote; a fuller walkthrough is here: https://pointchecknote.com/en/posts/2026-08-05-playwright-mcp-claude/
SOCIAL SHARE CARD GENERATOR