Playwright MCP Server
# Playwright MCP Server ðŸŽ
[](https://smithery.ai/server/@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, generate test code, web scraps the page 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](https://executeautomation.github.io/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/server/@executeautomation/playwright-mcp-server):
```bash
npx -y @smithery/cli install @executeautomation/playwright-mcp-server --client claude
```
#### Installation in VS Code
Install the Playwright MCP server in VS Code using one of these buttons:
<!--
// Generate using?:
const config = JSON.stringify({ name: 'playwright', command: 'npx', args: ["-y", "@executeautomation/playwright-mcp-server"] });
const urlForWebsites = `vscode:mcp/install?${encodeURIComponent(config)}`;
// Github markdown does not allow linking to `vscode:` directly, so you can use our redirect:
const urlForGithub = `https://insiders.vscode.dev/redirect?url=${encodeURIComponent(urlForWebsites)}`;
-->
[<img alt="Install in VS Code Insiders" src="https://img.shields.io/badge/VS_Code_Insiders-VS_Code_Insiders?style=flat-square&label=Install%20Server&color=24bfa5">](https://insiders.vscode.dev/redirect?url=vscode-insiders%3Amcp%2Finstall%3F%257B%2522name%2522%253A%2522playwright%2522%252C%2522command%2522%253A%2522npx%2522%252C%2522args%2522%253A%255B%2522-y%2522%252C%2522%2540executeautomation%252Fplaywright-mcp-server%2522%255D%257D)
Alternatively, you can install the Playwright MCP server using the VS Code CLI:
```bash
# For VS Code
code --add-mcp '{"name":"playwright","command":"npx","args":["@executeautomation/playwright-mcp-server"]}'
```
```bash
# For VS Code Insiders
code-insiders --add-mcp '{"name":"playwright","command":"npx","args":["@executeautomation/playwright-mcp-server"]}'
```
After installation, the ExecuteAutomation Playwright MCP server will be available for use with your GitHub Copilot agent in VS Code.
## 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"]
}
}
}
```
## Testing
This project uses Jest for testing. The tests are located in the `src/__tests__` directory.
### Running Tests
You can run the tests using one of the following commands:
```bash
# Run tests using the custom script (with coverage)
node run-tests.cjs
# Run tests using npm scripts
npm test # Run tests without coverage
npm run test:coverage # Run tests with coverage
npm run test:custom # Run tests with custom script (same as node run-tests.cjs)
```
The test coverage report will be generated in the `coverage` directory.
## Star History
[](https://star-history.com/#executeautomation/mcp-playwright&Date)
TDQS
Scored across 29 tools
Most tools have distinct purposes, with clear separation between browser actions (click, fill, navigate), HTTP methods (get, post, put), and code generation sessions. However, some overlap exists between playwright_click and playwright_iframe_click, and between playwright_get_visible_html and playwright_get_visible_text, which could cause minor confusion.
Tool names follow a highly consistent snake_case pattern with clear verb_noun structure. All browser interaction tools use 'playwright_' prefix followed by action verbs (click, fill, navigate), HTTP tools use 'playwright_' plus HTTP method (get, post, put), and codegen tools use descriptive action_session patterns (start_codegen_session, end_codegen_session).
With 29 tools, this is borderline heavy for a Playwright automation server. While Playwright has many capabilities, the count feels excessive compared to typical well-scoped servers (3-15 tools). Some tools could potentially be consolidated or parameterized to reduce the surface area.
The tool surface provides comprehensive coverage for browser automation and testing. It includes navigation, interaction (click, fill, hover, drag), HTTP operations (all major methods), debugging (logs, screenshots, PDF), assertions, iframe handling, and code generation workflows. No obvious gaps exist for typical Playwright use cases.