skillpack.co
All solutions

Playwright MCP

active

Microsoft's official MCP server for Playwright. Uses accessibility snapshots instead of screenshots for structured browser control. Auto-configured in GitHub Copilot's Coding Agent.

Score 93

Where it wins

Microsoft/Playwright official backing

Accessibility snapshots instead of screenshots — more reliable for structured tasks

Auto-configured in GitHub Copilot Coding Agent

MCP-native — works with any MCP-compatible host

Where to be skeptical

Token-heavy: 114K tokens/session vs 27K via CLI — well-documented 4x bloat problem

Less vision-aware than Browser Use for visual tasks

Accessibility snapshots miss visual layout information

Editorial verdict

Highest raw downloads in category (1.38M npm/wk). Cross-browser (Chromium + Firefox + WebKit). CLI mode is the token-efficient choice — 4x reduction vs MCP confirmed by 13+ independent sources. Microsoft officially recommends CLI for coding agents.

Videos

Reviews, tutorials, and comparisons from the community.

AI-Powered Test Automation with Playwright MCP, GitHub Copilot & VSCode (Playwright + TypeScript)

SDET- QA·2025-06-10

Let AI Explore Your Site & Write Tests with Playwright MCP!

Playwright·2025-06-16

How to Generate Playwright Tests using MCP + Copilot

Playwright·2025-05-15

Related

Public evidence

strong2026-03
4x token reduction (CLI vs MCP) — 13+ independent confirmations

Playwright MCP burns 114K tokens/session; CLI uses 27K (4x reduction). Microsoft officially recommends CLI for coding agents. Settled consensus across 13+ independent sources — not a debate.

13+ independent sources in Feb-Mar 2026Better Stack, Pramod Dutta, Microsoft official, and 10+ others
strongSelf-reported2026-03
Microsoft official recommendation: CLI for coding agents

Microsoft now officially recommends CLI for coding agent workflows and MCP for richer introspection loops. CLI companion makes Playwright the only tool that owns both sides of the CLI-over-MCP divide.

Official Microsoft documentationMicrosoft (official Playwright team)
strongSelf-reported2026-03
Cross-browser support — only ranked tool with Firefox + WebKit

Only ranked tool supporting Chromium, Firefox, and WebKit. 25 open issues is the fewest in the category, indicating the most polished/mature codebase. Auto-configured in GitHub Copilot Coding Agent.

29.3K stars, 2.3K forks, 25 open issues (fewest — indicates maturity)Microsoft (official Playwright team)
strong2025-04
HN front page: 'Playwright Tools for MCP' launch thread

Playwright MCP launch hit the HN front page. Discussion covered real-world usage with Claude Code and automatic test validation workflows, signaling strong developer interest in accessibility-tree-based browser automation.

181 HN points, 34 commentsHN community (submitted by alex_hirner)
strong2025-01
Speakeasy analysis: 'The Playwright proliferation problem with MCP'

Independent analysis showing Playwright MCP's 26-tool surface causes agent decision paralysis, and reducing to 8 core tools dramatically improves performance. Validates Playwright MCP as the de facto browser-automation MCP standard others benchmark against.

Widely referenced in MCP design discussionsNolan Sullivan (Speakeasy)
strong2025-09
GitHub Blog: How to debug a web app with Playwright MCP and GitHub Copilot

Step-by-step demo of Copilot agent mode using Playwright MCP to reproduce bugs, inspect live pages via accessibility snapshots, identify fixes, and verify them — all autonomously. Shows institutional commitment to Playwright MCP as the browser layer.

GitHub official engineering blogChristopher Harrison (Senior Developer Advocate, GitHub)
moderate2025-03
Simon Willison: microsoft/playwright-mcp — launch day coverage

Launch-day coverage noting Playwright MCP uses accessibility tree instead of screenshots. Early independent validation from a respected voice in developer tooling.

Simon Willison's blog (massive organic reach)Simon Willison (Django co-creator, independent)

Raw GitHub source

GitHub README peek

Constrained peek so you can sanity-check the source material without leaving the site.

Playwright MCP

A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.

Playwright MCP vs Playwright CLI

This package provides MCP interface into Playwright. If you are using a coding agent, you might benefit from using the CLI+SKILLS instead.

  • CLI: Modern coding agents increasingly favor CLI–based workflows exposed as SKILLs over MCP because CLI invocations are more token-efficient: they avoid loading large tool schemas and verbose accessibility trees into the model context, allowing agents to act through concise, purpose-built commands. This makes CLI + SKILLs better suited for high-throughput coding agents that must balance browser automation with large codebases, tests, and reasoning within limited context windows.<br>Learn more about Playwright CLI with SKILLS.

  • MCP: MCP remains relevant for specialized agentic loops that benefit from persistent state, rich introspection, and iterative reasoning over page structure, such as exploratory automation, self-healing tests, or long-running autonomous workflows where maintaining continuous browser context outweighs token cost concerns.

Key Features
  • Fast and lightweight. Uses Playwright's accessibility tree, not pixel-based input.
  • LLM-friendly. No vision models needed, operates purely on structured data.
  • Deterministic tool application. Avoids ambiguity common with screenshot-based approaches.
Requirements
  • Node.js 18 or newer
  • VS Code, Cursor, Windsurf, Claude Desktop, Goose, Junie or any other MCP client
<!-- // Generate using: node utils/generate-links.js -->
Getting started

First, install the Playwright MCP server with your client.

Standard config works in most of the tools:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
<details> <summary>Amp</summary>

Add via the Amp VS Code extension settings screen or by updating your settings.json file:

"amp.mcpServers": {
  "playwright": {
    "command": "npx",
    "args": [
      "@playwright/mcp@latest"
    ]
  }
}

Amp CLI Setup:

Add via the amp mcp addcommand below

amp mcp add playwright -- npx @playwright/mcp@latest
</details> <details> <summary>Antigravity</summary>

Add via the Antigravity settings or by updating your configuration file:

{
  "mcpServers": {
    "playwright": {
      "command": "npx",
      "args": [
        "@playwright/mcp@latest"
      ]
    }
  }
}
</details> <details> <summary>Claude Code</summary>

Use the Claude Code CLI to add the Playwright MCP server:

claude mcp add playwright npx @playwright/mcp@latest
</details> <details> <summary>Claude Desktop</summary>

Follow the MCP install guide, use the standard config above.

</details> <details> <summary>Cline</summary>

Follow the instruction in the section Configuring MCP Servers

Example: Local Setup

Add the following to your cline_mcp_settings.json file:

{
  "mcpServers": {
    "playwright": {
      "type": "stdio",
      "command": "npx",
      "timeout": 30,
      "args": [
        "-y",
        "@playwright/mcp@latest"
      ],
      "disabled": false
    }
  }
}
</details> <details> <summary>Codex</summary>
View on GitHub →