What it takes off you is the driving: open the page, find the control, fill the form, then check what actually happened — against the live page rather than fetched HTML. Every action returns the Playwright line that performed it, so the session reads back as code afterwards.
Microsoft's own MCP server for Playwright. It drives a real browser and works off the page's accessibility snapshot, so an agent addresses named elements instead of coordinates. Twenty-four tools are on by default; another forty-five sit behind `--caps`.
- Navigate, click, hover, type, press keys, select options, drag and drop, upload a file, handle a dialog, and fill a whole form in one call (`browser_navigate`, `browser_click`, `browser_fill_form`, `browser_file_upload`, `browser_handle_dialog`)
- An accessibility snapshot of the page, plus a search over it that returns matching nodes with their surrounding context (`browser_snapshot`, `browser_find`)
- Console messages, a numbered list of network requests, and the full detail of any one of them (`browser_console_messages`, `browser_network_requests`, `browser_network_request`)
- Screenshots, resizing, waiting for text to appear or disappear, tab management, and JavaScript evaluated on the page or a single element (`browser_take_screenshot`, `browser_wait_for`, `browser_tabs`, `browser_evaluate`)
- Seventeen storage tools behind `--caps=storage`: cookies and local and session storage read, set, deleted and cleared, plus a whole storage state saved and restored — which is how a logged-in session is reused instead of re-entered
- Four network tools behind `--caps=network`: routes that mock a URL pattern with your own status, body and headers, listed and removed, and the browser switched offline
- Eleven DevTools tools behind `--caps=devtools`: tracing started and stopped, video recording with chapters, and elements highlighted or annotated on the page
- Five assertion tools behind `--caps=testing` for checking an element, a list, a text or a value is visible, plus a locator generated for it — the pieces of a test rather than a click
- Coordinate-based mouse control behind `--caps=vision`, PDF export behind `--caps=pdf`, and the resolved configuration read back behind `--caps=config`
Node.js 18 or newer and npx — nothing else. It starts as a local process and talks to the client over stdio, so the browser it drives is the one on that machine. One thing to know before running two clients at once: a persistent profile can only be used by one browser instance at a time, so give each extra client `--isolated` or its own `--user-data-dir`. Extra capabilities come from `--caps` as a comma-separated list, or the `PLAYWRIGHT_MCP_CAPS` environment variable.
One command — npx @playwright/mcp@latest