A
licenseC
qualityD
maintenanceAn MCP server that gives Claude Code real browser control for web automation, testing, and screenshots.
32
23 npm
151
MIT
playwright-mcp
by ademdeniz
Related Servers
Alternatives to playwright-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI-powered browser automation, web scraping, and testing using Playwright across Chromium, Firefox, and WebKit. It allows users to perform actions like navigation, clicking, typing, and taking screenshots through natural language interfaces.6 npmMIT
- FlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to perform web automation tasks such as navigation, clicking, and taking screenshots by running Playwright on Cloudflare Workers. It allows models to interact with the web through a set of browser control tools across platforms like Claude Desktop and GitHub Copilot.-
- AlicenseAqualityCmaintenanceA lean, LLM-first browser automation MCP server that gives Claude (or any MCP client) a real Chromium browser to navigate, interact with, and debug web apps.149 npm6MIT
- AlicenseNot gradedqualityNot gradedmaintenanceA Playwright-based MCP server that exposes a live browser as a traceable, inspectable, debuggable and controllable execution environment for AI agents.3,661 npm57-
- FlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to automate browser testing via Chromium, providing tools for navigation, interaction, and inspection.-
TDQS
A4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clear, distinct purpose: navigating, reading state, capturing visuals, interacting, executing custom JS, asserting conditions, and closing the browser. No two tools overlap in function.
Naming Consistency5/5
All tool names follow an imperative verb pattern with consistent snake_case (e.g., get_page_state, close_browser). Even single-word names like navigate and click are verbs, maintaining a uniform style.
Tool Count5/5
8 tools is well-scoped for a browser automation server, covering navigation, interaction, inspection, visualization, scripting, verification, and teardown without bloat or redundancy.
Completeness4/5
The tool surface covers the core browser automation lifecycle (navigate, interact, observe, assert, cleanup). Missing explicit waits or advanced interactions (hover, dropdowns) but these are workable via evaluate, so gaps are minor.
Maintenance
ActivitySlowing
ResponsivenessNo issues