Draft: some verdicts here are not yet reviewed. Hidden from search engines.
Category · Checked
Browser automation with MCP servers
Servers that let an AI open, read and test web pages. 3 of 3 have an official server from the vendor.
Playwright has an official MCP server published by Microsoft (microsoft/playwright-mcp, npm @playwright/mcp). It runs locally on your machine over stdio via npx, needs no account or API key, and drives a real browser. Caveat: the project states it is not a security boundary, and it has no server-wide read-only mode.
Chrome DevTools has an official MCP server (chrome-devtools-mcp) published by Google's ChromeDevTools organization and announced on developer.chrome.com. It runs locally via npx, needs no account, and controls a live Chrome for debugging, performance traces and automation. Caveats: it exposes browser content to the client, and usage statistics are on by default.
Apple's WebKit team publishes a Safari MCP server built into safaridriver, introduced in Safari 27 and Safari Technology Preview 247. It runs locally on a Mac, exposes 17 tools for debugging pages, and needs remote automation enabled in Safari's Developer settings. The server has no sign-in. It can run JavaScript and click through pages.