TOOLKIT
Playwright MCP
Microsoft’s official browser server for agents: 71 tools over a real Chromium, driven by the accessibility tree rather than screenshots, so an SEO skill can render a page the way a crawler cannot.
by Microsoft (official)microsoft/playwright-mcpApache-2.0 licence37.0k starscommit 8a13ef8read by us 11 September 2026
What a marketing agent uses it for: rendering a page after JavaScript to compare with the raw HTML, reading the accessibility tree that agent-friendliness audits score, taking the screenshot a report needs, and checking a checkout flow step by step. Several skills on this shelf call Playwright through their own scripts; this server gives any agent the same browser directly.
It is a general automation tool with cookies, storage, network routing, recording, tracing and coordinate clicks, so the safety question is scope, not code: it does whatever a browser does, on whatever site the prompt names, with whatever profile you give it.
Microsoft’s own README recommends the Playwright CLI with skills over MCP for coding agents, because MCP loads large tool schemas and accessibility trees into context. For an occasional render inside a marketing task, MCP is fine.
What it exposes
71 tools, and which ones change things
Some of the 71: browser_navigate browser_snapshot browser_take_screenshot browser_click browser_fill_form browser_evaluate browser_network_requests browser_console_messages browser_pdf_save browser_verify_text_visible
Writes
- anything a browser can submit; use --isolated and a clean profile for audits
Pairs with
Skills that work on what it reads
- seo-technicalA nine-category technical audit: crawlability, indexability, security, URLs, mobile, Core Web Vitals, structured data, JavaScript rendering and IndexNow.
- seo-auditA full-site SEO audit that crawls, delegates to specialists and returns a 0 to 100 health score.
- croA page review in seven dimensions ordered by impact: value proposition, headline, CTA hierarchy, scannability, trust, objections, friction. Output in four bands: quick wins, high-impact changes, test ideas, copy alternatives.
Method behind it
Our Core Web Vitals glossary explains why a single Playwright run is a lab number and not the field number Google ranks on. Use the browser for rendering and screenshots; use CrUX for the metric.
What are Core Web VitalsQuestions
Questions people ask before installing
Do I need it if I use the claude-seo plugin?
claude-seo bundles its own Playwright inside its runtime for render_page.py and screenshots. This server is for agents and skills that do not ship a browser.
Will it use my logged-in browser?
By default it runs its own Chromium with a persistent profile. It can connect to your running browser through an extension if you ask; for audits, prefer --isolated.
Is it the same as Playwright CLI?
Same engine, different interface. Microsoft suggests the CLI plus skills for token-heavy coding work and MCP for loops that need persistent browser state.