Playwright MCP Server
# Playwright MCP Server
[](https://smithery.ai/protocol/@executeautomation/playwright-mcp-server)
A Model Context Protocol server that provides browser automation capabilities using Playwright. This server enables LLMs to interact with web pages, take screenshots, and execute JavaScript in a real browser environment.
<a href="https://glama.ai/mcp/servers/yh4lgtwgbe"><img width="380" height="200" src="https://glama.ai/mcp/servers/yh4lgtwgbe/badge" alt="mcp-playwright MCP server" /></a>
## Screenshot

## [Documentation](https://executeautomation.github.io/mcp-playwright/) | [API reference](http://localhost:3000/mcp-playwright/docs/playwright-web/Supported-Tools)
## Installation
You can install the package using either npm, mcp-get, or Smithery:
Using npm:
```bash
npm install -g @executeautomation/playwright-mcp-server
```
Using mcp-get:
```bash
npx @michaellatman/mcp-get@latest install @executeautomation/playwright-mcp-server
```
Using Smithery
To install Playwright MCP for Claude Desktop automatically via [Smithery](https://smithery.ai/protocol/@executeautomation/playwright-mcp-server):
```bash
npx @smithery/cli install @executeautomation/playwright-mcp-server --client claude
```
## Configuration to use Playwright Server
Here's the Claude Desktop configuration to use the Playwright server:
```json
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["-y", "@executeautomation/playwright-mcp-server"]
}
}
}
```
TDQS
Scored across 12 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools cleanly separate into three categories: HTTP methods (GET, POST, PUT, PATCH, DELETE), browser interaction (click, fill, hover, navigate, screenshot, select), and JavaScript execution (evaluate). There is no overlap between these functional areas.
All tools follow a perfect 'playwright_verb' naming pattern with consistent snake_case throughout. The verb choices are precise and descriptive (click, fill, hover, navigate, evaluate, screenshot, select, get, post, put, patch, delete), creating a highly predictable and readable naming convention.
12 tools is well-scoped for a Playwright automation server. The count provides comprehensive coverage of core browser automation and HTTP testing capabilities without being overwhelming. Each tool clearly earns its place in the toolkit.
The tool surface is nearly complete for browser automation and HTTP testing. It covers navigation, interaction, JavaScript execution, screenshots, and full HTTP method support. Minor gaps might include waiting/retry mechanisms or file upload/download operations, but core workflows are well covered.