Playwright MCP
Browser automation for AI agents via Microsoft Playwright
How to Install Playwright MCP
$npx @playwright/mcp@latestRequires Claude Desktop, Cursor, Windsurf, or another MCP-compatible client.
About Playwright MCP
Microsoft's official Playwright MCP server gives AI agents full browser automation — navigating pages, clicking, typing, taking screenshots, and extracting structured data. Built on Playwright's battle-tested cross-browser engine with Chromium, Firefox, and WebKit support.
Playwright MCP is a Browser Automation MCP server designed for QA, growth, ops, and research teams. It enables driving a real browser from an AI assistant by exposing Playwright/Puppeteer sessions as MCP tools. Key capabilities include navigate, click, type, and submit, headless screenshots and pdfs, form-fill and file-upload flows, and structured tool calls that work cleanly inside an LLM context. It integrates with Playwright, Puppeteer, headless Chromium, and Selenium grids, and is best suited for QA, growth, ops, and research teams who need end-to-end testing.
Key Features
- browser-automation
- playwright
- microsoft
- scraping
- testing
Pricing
- Core MCP server
- Community support
- Works with any MCP client
- Everything in Free
- Higher usage limits
- Priority support
- Everything in Pro
- SLA & SSO
- Dedicated support
Tier details are indicative — visit the Playwright MCP website for current pricing.
Pros & Cons
Pros
- Reaches sites that don't expose APIs
- Self-healing test flows
- Strong selectors paired with LLM context
Cons
- Slower than direct API calls
- Brittle against aggressive bot protection
- Per-session state can leak without isolation
Best For
- End-to-end testing
- Scraping rendered pages
- Form-heavy workflows
- Dashboard data extraction
Screenshots
Screenshots coming soon —
Submit yours →Our Take on Playwright MCP
The definitive browser automation MCP — more capable and better maintained than Puppeteer MCP.