MCP-Server-Playwright
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_navigateC | Navigate to a URL |
| browser_screenshotB | Take a screenshot of the current page or a specific element |
| browser_clickB | Click an element on the page using CSS selector |
| browser_click_textB | Click an element on the page by its text content |
| browser_fillB | Fill out an input field |
| browser_selectC | Select an element on the page with Select tag using CSS selector |
| browser_select_textC | Select an element on the page with Select tag by its text content |
| browser_hoverA | Hover an element on the page using CSS selector |
| browser_hover_textB | Hover an element on the page by its text content |
| browser_evaluateC | Execute JavaScript in the browser console |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose. Pairwise similar tools like click and click_text are differentiated by CSS selector vs text content, making ambiguity minimal.
All tools follow a consistent 'browser_verb' pattern, with optional '_text' suffix for text-based selectors. Snake_case is used uniformly.
10 tools is an appropriate number for browser automation, covering essential actions without being overwhelming. The scope is well-defined.
The set covers core browser interactions (navigation, click, fill, select, hover, evaluate, screenshot). Missing operations like waiting, scrolling, or keyboard input are minor gaps.