Best Playwright MCP Servers in 2026
Microsoft's Playwright MCP became the default way to give an agent a browser: accessibility-tree-based interaction instead of fragile screenshots, so the agent can click, type, and assert reliably.
Beyond the official server, community builds add record-replay, network interception, and multi-tab support. The options below are ranked by adoption; the browser-automation category page covers hosted alternatives for anti-bot-heavy targets.

Playwright MCP server

Playwright Model Context Protocol Server - Tool to automate Browsers and APIs in Claude Desktop, Cline, Cursor IDE and More 🔌

Chrome extension & CLI to let agents control your browser. Runs Playwright snippets in a stateful sandbox. Available as CLI or MCP

MCP server for fetch web page content using Playwright headless browser.

这是一款基于 Playwright 开发的小红书自动搜索和评论工具,作为 MCP Server,可通过特定配置接入 MCP Client(如Claude for Desktop),帮助用户自动完成登录小红书、搜索关键词、获取笔记内容及发布AI生成评论等操作。

MCP Server Playwright A Model Context Protocol server that provides browser automation capabilities using Playwright Enable LLMs to interact with web pages, take screenshots, and execute JavaScript...

This project leverages Playwright for automated browser testing and integrates with Cloudflare Workers, Browser Rendering and @cloudflare/playwright for deployment.

The server implements a simple note storage system with: - Custom note:// URI scheme for accessing individual notes - Each note resource has a name, description and text/plain mimetype

An MCP (Model Context Protocol) server that provides a persistent Playwright evaluation environment.

A Model Context Protocol server that provides browser automation capabilities using Playwright with Chrome DevTools Protocol (CDP) support.

A local-first Playwright test automation toolkit for AI coding agents (Cursor, Claude Code, Copilot), with MCP tools for codegen, browser control, and recordings.

Production-ready starter for with Playwright, TypeScript, Page Object Model, and AI-powered Claude Code agents via MCP.
FAQ
Why Playwright over screenshot-based browser agents?
Playwright MCP drives the browser through the accessibility tree — structured element references rather than pixel guessing. That makes interactions dramatically more reliable and cheaper in tokens than vision-based approaches.
Can it verify the app I am building?
Yes — this is its killer workflow. The agent writes code, starts your dev server, then uses Playwright MCP to load the page, click through the flow, and screenshot the result. Frontend verification without leaving the chat.
Does it need a display?
No, it runs headless by default. Most servers accept a --headed flag or a "take screenshot" tool when you want to watch or debug.