MCP server

Playwright MCP Server: Browser Automation for AI Coding Agents

The Playwright MCP server lets an AI coding agent drive a real browser through structured accessibility snapshots, so it can open pages, fill forms and check what it built.

Run
npx @playwright/mcp@latest
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the Playwright MCP server?

Playwright MCP is Microsoft's MCP server for browser automation. It exposes Playwright to an AI agent through accessibility snapshots instead of screenshots, so the agent can navigate, click, type and read pages without a vision model. You start it locally with npx @playwright/mcp@latest.

Playwright MCP is a Model Context Protocol server that gives an AI agent browser automation through Playwright. The README says it works from structured accessibility snapshots, so the agent reads the page as a tree of elements rather than guessing from pixels.

You run it locally with npx @playwright/mcp@latest. The agent can then open a URL, read the snapshot, click, type, fill forms and capture a screenshot to check the result. For a Chrome-only alternative, see Chrome DevTools MCP.

What it changes in your workflow

  • The agent can open the page it just built, click through the flow and report what broke, instead of you checking by hand.
  • It needs no vision model, because actions target element references from the accessibility snapshot.
  • Console messages and network requests are available as tools, so a failing script or a blocked request shows up in the agent's reasoning.
  • You can run it headless, in isolated sessions with no saved profile, or attach to a running Chrome or Edge through the Playwright Extension.

Local or remote

Playwright MCP
Where it runsOn your machine, started by the client with npx
Transportstdio by default; pass --port to serve HTTP at /mcp
BrowsersChrome, Firefox, WebKit and Edge through the --browser option
RequirementsNode.js 18 or newer and an MCP client
Account or keyNone for the server itself

Who it is for

Best for

  • Developers who want an agent to test a page or a flow in a real browser while it codes.
  • Exploratory automation and long agent loops that benefit from a persistent browser context.
  • Teams that want one server across VS Code, Cursor, Windsurf, Claude Desktop, Codex, Gemini CLI and other listed clients.

Not for

  • Token-tight coding sessions. The README itself points coding agents to Playwright CLI with skills, because CLI calls load fewer tokens than MCP tool schemas and snapshots.
  • A security boundary. The README states plainly that Playwright MCP is not one.
  • Pixel-level checks as a default. Screenshots exist, but the snapshot is the primary view; for layout diffs see Squint MCP.

Use it with UiChemy

Playwright MCP verifies pages in a browser. UiChemy produces them for WordPress: Composer writes HTML, CSS and JS inside Elementor or Gutenberg, and Figma to WordPress converts designs. Open the finished page with this server and have the agent click through it. Click Get Started on uichemy.com.