Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for builders who need browser automation that is structured, widely documented, and grounded in an official Playwright-maintained MCP surface rather than a fragile wrapper.
Where this stands now
microsoft/playwright-mcp ranks #12 of 1270 tracked Developer Tools items by composite score (8.6 against a section median of 4.9). The section currently carries 1032 Bronze, 134 Silver, 103 Gold, 1 Low Signal. RepoRadar has retained observations for this record since 2026-06-26 (99 days in the current window). Signal extremes versus the section: momentum at the 97th percentile; novelty at the 95th percentile.
Who should use it
Who should skip it
Skip microsoft/playwright-mcp if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
microsoft/playwright-mcp is tracked by RepoRadar as an MCP server in the Developer Tools section. First seen 2026-06-26; the source record was last checked on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for microsoft/playwright-mcp are workflow potential (10.0) and maturity (9.2), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The microsoft/playwright-mcp record combines a 8.6/10 composite score with separate popularity (100.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Questions worth asking before you adopt this
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
Browser automation can act inside logged-in sessions and persistent profiles, so start with isolated profiles or throwaway accounts; The README explicitly says Playwright MCP is not a security boundary, so host allowlists and client-side permissions still matter; The tool surface includes powerful non-read-only actions and an unsafe code-execution path inside the Playwright server process, so evaluate it on non-sensitive sites first.