Playwright MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port the auth gate binds to | 10000 |
| MCP_TOKEN | Yes | Required bearer token for authentication | |
| UPSTREAM_PORT | No | Loopback port the MCP server listens on | 8931 |
| PLAYWRIGHT_MCP_ALLOWED_HOSTS | No | Comma-separated list of allowed hosts |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| browser_closeB | Close the page |
| browser_resizeB | Resize the browser window |
| browser_console_messagesB | Returns all console messages |
| browser_handle_dialogC | Handle a dialog |
| browser_evaluateB | Evaluate JavaScript expression on page or element |
| browser_file_uploadB | Upload one or multiple files |
| browser_dropA | Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided. |
| browser_fill_formB | Fill multiple form fields |
| browser_press_keyB | Press a key on the keyboard |
| browser_typeB | Type text into editable element |
| browser_navigateC | Navigate to a URL |
| browser_navigate_backA | Go back to the previous page in the history |
| browser_network_requestsA | Returns a numbered list of network requests since loading the page. Use browser_network_request with the number to get full details. |
| browser_network_requestA | Returns full details (headers and body) of a single network request, or a single part if |
| browser_run_code_unsafeA | Run a Playwright code snippet. Unsafe: executes arbitrary JavaScript in the Playwright server process and is RCE-equivalent. |
| 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_snapshotB | Capture accessibility snapshot of the current page, this is better than screenshot |
| browser_clickB | Perform click on a web page |
| browser_dragA | Perform drag and drop between two elements |
| browser_hoverA | 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_forA | 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 23 tools
While most tools have distinct purposes, browser_type, browser_press_key, and browser_fill_form overlap in typing interactions, and browser_drop vs browser_drag could cause confusion. browser_run_code_unsafe is clearly distinct but its purpose is not aligned with typical browser automation.
All tools follow a consistent 'browser_' prefix with a clear verb_noun pattern (e.g., browser_navigate, browser_click, browser_take_screenshot). The naming is uniform and easy to predict.
23 tools is slightly above the typical well-scoped range (3-15), but given the breadth of browser automation (navigation, interaction, input, network, tabs), it is justified. The count is on the heavier side but not excessive.
The tool surface covers core browser automation needs: navigation, interactions, input, screenshots/snapshots, dialogs, uploads, downloads, and network inspection. Minor gaps exist such as cookie management and form reset, but agents can work around them using browser_run_code_unsafe.