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. The container refuses to start without it. | |
| 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_HOST | No | Only relevant when running the server directly outside this Docker image; ignored on Render because the entrypoint always passes equivalent CLI flags. | |
| PLAYWRIGHT_MCP_HEADLESS | No | Only relevant when running the server directly outside this Docker image; ignored on Render because the entrypoint always passes equivalent CLI flags. | |
| PLAYWRIGHT_MCP_NO_SANDBOX | No | Only relevant when running the server directly outside this Docker image; ignored on Render because the entrypoint always passes equivalent CLI flags. | |
| PLAYWRIGHT_MCP_ALLOWED_HOSTS | No | Comma-separated hostnames to allow for the host check (e.g. myapp.com,myapp.onrender.com; * disables the check). Required if using a custom domain, as the entrypoint only auto-allows your service's onrender.com hostname via RENDER_EXTERNAL_HOSTNAME. |
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
Each tool maps to a distinct browser action or state source, and the descriptions generally make boundaries clear. The only mild friction is between browser_type, browser_fill_form, and browser_evaluate, but their usage contexts differ enough to avoid serious misselection.
All tools share a consistent browser_ prefix and snake_case style, which gives the set a predictable feel. A few noun-style tools like browser_tabs, browser_console_messages, and browser_network_requests break the otherwise dominant action-focused pattern, but the deviation is minor.
At 23 tools, the surface feels heavy and sits in the 16-25 range that reads as over-scoped. The browser-automation domain is broad enough that most tools justify their existence, but some consolidation might improve the set's overall tightness.
The surface covers the major browser workflow: navigation, interaction, form filling, waiting, screenshots, snapshots, console/network inspection, dialogs, tabs, and file upload. Minor gaps like reload, forward navigation, and cookie/storage management remain, but agents can work around them with navigate or browser_evaluate.