Playwright Plus Python MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | Your token used for publishing to PyPI. | |
| UV_PUBLISH_PASSWORD | No | Your password for publishing to PyPI. | |
| UV_PUBLISH_USERNAME | No | Your username for publishing to PyPI. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playwright_navigateC | Navigate to a URL,thip op will auto create a session |
| playwright_screenshotC | Take a screenshot of the current page or a specific element |
| playwright_clickC | Click an element on the page using CSS selector |
| playwright_fillC | Fill out an input field |
| playwright_evaluateC | Execute JavaScript in the browser console |
| playwright_click_textB | Click an element on the page by its text content |
| playwright_get_text_contentB | Get the text content of all elements |
| playwright_get_html_contentC | Get the HTML content of the page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap between playwright_click and playwright_click_text, which could cause confusion about when to use each. The other tools are clearly differentiated by their specific actions like navigation, evaluation, or content retrieval.
All tool names follow a consistent snake_case pattern with the prefix 'playwright_' followed by a descriptive verb or verb_noun combination. This uniformity makes the tool set predictable and easy to understand at a glance.
With 8 tools, this server is well-scoped for browser automation tasks, covering essential actions like clicking, navigating, evaluating JavaScript, and retrieving content. Each tool serves a clear purpose without being overly complex or sparse.
The tool set covers core browser automation workflows, including navigation, interaction, and content extraction. However, there are minor gaps, such as the lack of tools for handling pop-ups, managing cookies, or performing drag-and-drop actions, which could limit some advanced automation scenarios.