playwright-mcp-humanized
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAYWRIGHT_MCP_EXTENSION_TOKEN | No | Token required when using the `--extension` flag to connect to the Playwright Chrome Extension. If you are not using extension mode, this can be omitted. |
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_findA | Search the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref. |
| 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 24 tools
Most tools are clearly distinct (navigate, click, snapshot, screenshot, wait, tabs), but a few pairs could be confused: browser_evaluate vs browser_run_code_unsafe both execute JavaScript, and browser_drag vs browser_drop both describe drag/drop behavior. The descriptions do enough to clarify most boundaries.
All tools share the consistent browser_ prefix and snake_case style, which creates a predictable pattern. Minor deviations exist where some tools are noun-phrases rather than verb commands (browser_network_requests, browser_tabs, browser_snapshot), but these are not disruptive.
At 24 tools, the set is on the heavy side for the border of the recommended range. The domain is broad enough to justify many of them, but there is some redundancy (fill_form vs type, drag vs drop, evaluate vs run_code_unsafe) that makes the count feel slightly inflated.
The set covers the major browser automation lifecycle: navigation, interaction, form filling, waiting, snapshots, screenshots, console/network inspection, dialogs, tabs, and uploads. The main gap is browser forward navigation, and there is no dedicated reload action, but these can be worked around with browser_navigate or browser_run_code_unsafe.