Playwright Server 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. | |
| UV_PUBLISH_PASSWORD | No | Your password for publishing. | |
| UV_PUBLISH_USERNAME | No | Your username for publishing. |
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 targeting different page interactions (clicking, filling, navigating, etc.), but 'playwright_get_html_content' and 'playwright_get_text_content' could potentially be confused as both retrieve content from the page, though their descriptions clarify the difference. Overall, the overlap is minimal and manageable.
All tool names follow a consistent 'playwright_' prefix with snake_case and clear verb_noun patterns (e.g., playwright_click, playwright_navigate). This predictability makes it easy for agents to understand and select tools without confusion.
With 8 tools, this server is well-scoped for a Playwright automation purpose, covering essential actions like navigation, interaction, content retrieval, and screenshots. Each tool serves a clear, necessary function without bloat or redundancy.
The toolset covers core web automation tasks effectively, including navigation, element interaction, content extraction, and screenshots. A minor gap exists in advanced operations like handling pop-ups, waiting for elements, or managing sessions explicitly, but agents can likely work around these with the provided tools.