Playwright MCP
Microsoft's MCP server that drives a real browser via Playwright — Chromium, Firefox, and WebKit. Ships ~22 tools that operate against the page's accessibility tree rather than pixel coordinates, which is dramatically more reliable than screenshot-and-click loops. The default web automation MCP for agents that need to read DOM and follow real navigation.
Overview
Microsoft's MCP server that drives a real browser via Playwright — Chromium, Firefox, and WebKit. Ships ~22 tools that operate against the page's accessibility tree rather than pixel coordinates, which is dramatically more reliable than screenshot-and-click loops. The default web automation MCP for agents that need to read DOM and follow real navigation.
Stack & relationships
How Playwright MCP relates to other entries in the catalog — recommended pairings, alternatives, dependencies, and edges to avoid. Each edge carries a one-line operator note from our editorial team.
Alternatives
- Alternative toMCP Fetch Server
Fetch is for static HTML; Playwright handles JS-rendered pages, auth flows, and forms. Pick Playwright when readability extraction isn't enough.
- Alternative toFirecrawl MCP
Firecrawl outsources rendering to a managed cloud — handles anti-bot evasion at scale. Playwright keeps the browser local. Pick Firecrawl for crawl-volume scenarios; Playwright for single-page automation.
Pros
- Accessibility-tree targeting beats coordinate clicking
- Chromium, Firefox, WebKit covered
- Maintained by Microsoft (Playwright authors)
Cons
- Heavy: real browser process per session
- Stateful — agents need to manage tab lifetimes carefully
Compatibility
| Operating systems | macOS Linux Windows |
| GPU backends | n/a |
| License | Open source · free (OSS, Apache 2.0) |
Get Playwright MCP
Frequently asked
Is Playwright MCP free?
What operating systems does Playwright MCP support?
Which GPUs work with Playwright MCP?
Reviewed by RunLocalAI Editorial. See our editorial policy for how we evaluate tools.