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; Render routes to it. | 10000 |
| MCP_TOKEN | Yes | Required. Bearer token every request must present. Generated by Render at deploy time. The container refuses to start without it. Rotate by editing the value in the Dashboard and updating your clients. | |
| UPSTREAM_PORT | No | Loopback port the MCP server listens on behind the gate. Change only if it collides with something inside the container. | 8931 |
| PLAYWRIGHT_MCP_ALLOWED_HOSTS | No | Comma-separated list of allowed hosts for the host check (e.g. myapp.com,myapp.onrender.com; * disables the check). Set this if you add a custom domain. |
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
Most tools have clearly distinct browser actions and resources, with descriptions that help distinguish similar-sounding pairs. A few boundaries are softer, such as browser_drag vs browser_drop, browser_snapshot vs browser_take_screenshot, and browser_evaluate vs browser_run_code_unsafe, but these are mostly clarified by descriptions.
All tools use a consistent browser_ prefix and snake_case, making the set predictable overall. Minor deviations exist: browser_tabs is a multiplexed noun-style tool, and a few read-only tools use noun phrases (browser_console_messages, browser_network_requests) rather than verb_noun action names.
With 23 tools, the server is on the heavy side but still reasonably scoped for a full browser-automation surface. Each tool maps to a meaningful capability, though some could arguably be consolidated, such as fill_form/type/press_key or the network request pair.
The surface covers most browser-automation workflows: navigation, interaction, forms, uploads, drag/drop, snapshots, screenshots, console, network inspection, tabs, dialogs, and evaluation. Minor gaps remain, such as explicit forward navigation and cookie/storage management, but agents can generally work around these.