Playwright Server
# playwright-server MCP server
\A MCP server with playwright tools\
<a href="https://glama.ai/mcp/servers/c50bsocgzb"><img width="380" height="200" src="https://glama.ai/mcp/servers/c50bsocgzb/badge" alt="Playwright Server MCP server" /></a>
<a href="https://smithery.ai/server/@williamvd4/playwright-plus-python-mcp"><img alt="Smithery Badge" src="https://smithery.ai/badge/@williamvd4/playwright-plus-python-mcp"></a>
## Components
### Resources
The server implements a simple note storage system with:
- Custom note:// URI scheme for accessing individual notes
- Each note resource has a name, description and text/plain mimetype
### Prompts
The server provides a single prompt:
- summarize-notes: Creates summaries of all stored notes
- Optional "style" argument to control detail level (brief/detailed)
- Generates prompt combining all current notes with style preference
### Tools
The server implements the following tools:
- `playwright_navigate`: Navigates to a specified URL. This operation will automatically create a new session if there is no active session.
- Requires a `url` argument (string).
- `playwright_screenshot`: Takes a screenshot of the current page or a specific element.
- Requires a `name` argument (string) for the screenshot file name.
- Optional `selector` argument (string) to specify a CSS selector for the element to screenshot. If no selector is provided, a full-page screenshot is taken.
- `playwright_click`: Clicks an element on the page using a CSS selector.
- Requires a `selector` argument (string) to specify the CSS selector for the element to click.
- `playwright_fill`: Fills out an input field.
- Requires a `selector` argument (string) to specify the CSS selector for the input field.
- Requires a `value` argument (string) to specify the value to fill.
- `playwright_evaluate`: Executes JavaScript code in the browser console.
- Requires a `script` argument (string) to specify the JavaScript code to execute.
- `playwright_click_text`: Clicks an element on the page by its text content.
- Requires a `text` argument (string) to specify the text content of the element to click.
- `playwright_get_text_content`: Get the text content of all visiable elements.
- `playwright_get_html_content`: Get the HTML content of the page.
- Requires a `selector` argument (string) to specify the CSS selector for the element.
## Configuration
[TODO: Add configuration details specific to your implementation]
## Quickstart
### Install
#### Claude Desktop
On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
<details>
<summary>Development/Unpublished Servers Configuration</summary>
```
"mcpServers": {
"playwright-server": {
"command": "uv",
"args": [
"--directory",
"C:\Users\xxxxx\Documents\project\python\mcp\playwright-server",
"run",
"playwright-server"
]
}
}
```
</details>
<details>
<summary>Published Servers Configuration</summary>
```
"mcpServers": {
"playwright-server": {
"command": "uvx",
"args": [
"playwright-server"
]
}
}
```
</details>
## Development
### Building and Publishing
To prepare the package for distribution:
1. Sync dependencies and update lockfile:
```bash
uv sync
```
2. Build package distributions:
```bash
uv build
```
This will create source and wheel distributions in the `dist/` directory.
3. Publish to PyPI:
```bash
uv publish
```
Note: You'll need to set PyPI credentials via environment variables or command flags:
- Token: `--token` or `UV_PUBLISH_TOKEN`
- Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
### Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging
experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
You can launch the MCP Inspector via [`npm`](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
```bash
npx @modelcontextprotocol/inspector uv --directory C:\Users\YUNYING\Documents\project\python\mcp\playwright-server run playwright-server
```
Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, playwright_click targets elements by CSS selector while playwright_click_text uses text content, and tools like playwright_get_html_content versus playwright_get_text_content provide different types of content retrieval. The descriptions clearly differentiate the specific actions each tool performs.
All tools follow a consistent 'playwright_verb' pattern with snake_case throughout. The naming is perfectly predictable, starting with 'playwright_' followed by an action verb that accurately describes the tool's function, such as 'click', 'evaluate', 'fill', or 'navigate'.
With 8 tools, this server is well-scoped for browser automation tasks. Each tool earns its place by covering essential operations like navigation, interaction (clicking, filling), content retrieval (HTML, text), and utilities (screenshot, JavaScript execution). This count is ideal for the domain without being overwhelming or insufficient.
The toolset covers core browser automation workflows effectively, including navigation, element interaction, content extraction, and screenshots. Minor gaps exist, such as no explicit tool for waiting or handling alerts, but agents can work around these using existing tools like playwright_evaluate for JavaScript-based solutions. The surface is largely complete for the stated purpose.