Playwright MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_closeA | Close the page |
| browser_resizeA | Resize the browser window |
| browser_console_messagesB | Returns all console messages |
| browser_handle_dialogC | Handle a dialog |
| browser_evaluateA | Evaluate JavaScript expression on page or element |
| browser_file_uploadB | Upload one or multiple files |
| browser_fill_formB | Fill multiple form fields |
| browser_installA | Install the browser specified in the config. Call this if you get an error about the browser not being installed. |
| browser_press_keyB | Press a key on the keyboard |
| browser_typeA | Type text into editable element |
| browser_navigateB | Navigate to a URL |
| browser_navigate_backA | Go back to the previous page |
| browser_network_requestsB | Returns all network requests since loading the page |
| browser_run_codeA | Run Playwright code snippet |
| browser_take_screenshotA | Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions. |
| browser_snapshotA | Capture accessibility snapshot of the current page, this is better than screenshot |
| browser_clickB | Perform click on a web page |
| browser_dragB | Perform drag and drop between two elements |
| browser_hoverB | Hover over element on page |
| browser_select_optionB | Select an option in a dropdown |
| browser_tabsA | List, create, close, or select a browser tab. |
| browser_wait_forB | Wait for text to appear or disappear or a specified time to pass |
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 22 tools
Most tools have distinct purposes, but there is some overlap between browser_snapshot and browser_take_screenshot, as both involve capturing page states, though their descriptions clarify different use cases. The tools generally target specific actions like navigation, interaction, or monitoring, reducing confusion.
All tool names follow a consistent 'browser_' prefix with snake_case, using clear verbs like click, close, navigate, or wait_for. This predictable pattern makes it easy for agents to understand and predict tool functions without ambiguity.
With 22 tools, the count is borderline high for a web automation server, potentially overwhelming but still manageable given the comprehensive scope. It covers many aspects of browser interaction, though some tools might be consolidated for better focus.
The tool set provides complete coverage for web automation tasks, including navigation, interaction (click, type, drag), form handling, monitoring (console, network), and utilities (screenshot, wait). No obvious gaps exist for typical Playwright workflows, ensuring agents can handle end-to-end scenarios.