microsoft/playwright-mcp

Playwright MCP server

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 55 minutes ago
Added to GitGenius on August 31st, 2026
Created on March 21st, 2025
Open Issues & Pull Requests: 8 (+0)
GitHub issues: Enabled
Number of forks: 3,113
Total Stargazers: 36,871 (+1)
Total Subscribers: 150 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.1 hours
Mean response time: 3.8 days
90th percentile: 5.9 days
Tracked items: 881

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 15% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 3
Closed in 7 days: 2
Avg open age: 18 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 3
Closed in 7 days: 2
Comments in 7 days: 1
Events in 7 days: 3

Top labels

  • triaging (57)
  • backlog (29)
  • collecting-feedback (27)
  • v-next (9)
  • open-to-pr (3)

Detailed Description

Playwright MCP is a Model Context Protocol server that enables large language models to automate web browser interactions using Playwright's accessibility tree rather than visual screenshots.

The tool solves the problem of giving LLMs deterministic, token-efficient access to web pages by exposing structured accessibility snapshots instead of pixel-based representations. This approach eliminates the need for vision models and reduces ambiguity in how models interpret and interact with page elements. The server translates Playwright's browser automation capabilities into MCP tools that agents can call through a standardized interface.

Developers should choose this tool when building exploratory automation workflows, self-healing tests, or long-running autonomous agents where maintaining continuous browser context and rich introspection of page structure justify the token cost of MCP's verbose tool schemas and accessibility trees. The README explicitly contrasts this with the Playwright CLI plus SKILLS approach, which is better suited for coding agents that need token efficiency and must balance browser automation with large codebases and reasoning within limited context windows. The MCP server is relevant for specialized agentic loops where iterative reasoning over page structure outweighs token cost concerns, whereas the CLI approach favors high-throughput agents using concise, purpose-built commands.

The project maintains active development with regular updates to keep pace with MCP client ecosystem changes. The tool is designed to work across multiple MCP-compatible clients including VS Code, Cursor, Claude Desktop, and others, suggesting ongoing attention to compatibility and integration patterns. TypeScript is used throughout, indicating a focus on type safety and developer experience for those building on top of the server.