mcp-playwright
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 |
|---|---|
| start_codegen_sessionC | Start a new code generation session to record Playwright actions |
| end_codegen_sessionC | End a code generation session and generate the test file |
| get_codegen_sessionC | Get information about a code generation session |
| clear_codegen_sessionC | Clear a code generation session without generating a test |
| playwright_navigateC | Navigate to a URL |
| playwright_screenshotC | Take a screenshot of the current page or a specific element |
| playwright_clickC | Click an element on the page |
| playwright_iframe_clickC | Click an element in an iframe on the page |
| playwright_iframe_fillC | Fill an element in an iframe on the page |
| playwright_fillC | fill out an input field |
| playwright_selectC | Select an element on the page with Select tag |
| playwright_hoverC | Hover an element on the page |
| playwright_upload_fileA | Upload a file to an input[type='file'] element on the page. In HTTP mode (disabled), provide an uploadResourceUri from construct_upload_url (preferred) or a reachable filePath. |
| playwright_evaluateC | Execute JavaScript in the browser console |
| playwright_console_logsC | Retrieve console logs from the browser with filtering options |
| playwright_closeB | Close the browser and release all resources |
| playwright_getC | Perform an HTTP GET request |
| playwright_postC | Perform an HTTP POST request |
| playwright_putC | Perform an HTTP PUT request |
| playwright_patchC | Perform an HTTP PATCH request |
| playwright_deleteC | Perform an HTTP DELETE request |
| playwright_expect_responseB | Ask Playwright to start waiting for a HTTP response. This tool initiates the wait operation but does not wait for its completion. |
| playwright_assert_responseB | Wait for and validate a previously initiated HTTP response wait operation. |
| playwright_custom_user_agentC | Set a custom User Agent for the browser |
| playwright_get_visible_textB | Get the visible text content of the current page |
| playwright_get_visible_htmlC | Get the HTML content of the current page. By default, all tags are removed from the output unless removeScripts is explicitly set to false. |
| playwright_go_backB | Navigate back in browser history |
| playwright_go_forwardA | Navigate forward in browser history |
| playwright_dragC | Drag an element to a target location |
| playwright_press_keyC | Press a keyboard key |
| playwright_save_as_pdfC | Save the current page as a PDF file |
| playwright_click_and_switch_tabA | Click a link and switch to the newly opened tab |
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 32 tools
Most tools have distinct purposes, but there is some overlap between HTTP request tools (get, post, put, patch, delete) and navigation/action tools that could cause confusion in selection. The codegen session tools are clearly separated from browser interaction tools, but within browser actions, some tools like playwright_click and playwright_iframe_click have similar purposes with minor context differences.
All tools follow a consistent snake_case naming convention with a clear 'playwright_' prefix for browser interaction tools and descriptive verb_noun patterns. The codegen session tools use similar patterns (clear_codegen_session, start_codegen_session, etc.), and HTTP tools maintain consistency (playwright_get, playwright_post, etc.).
With 32 tools, the count feels heavy for a Playwright automation server, suggesting potential over-fragmentation of functionality. While Playwright has many capabilities, this many tools might overwhelm agents and could be consolidated (e.g., HTTP methods into fewer tools). It's borderline excessive but still manageable.
The tool set provides comprehensive coverage for Playwright automation, including navigation, interaction, HTTP requests, iframe handling, code generation sessions, and utilities like screenshots and PDFs. There are no obvious gaps—it supports full browser automation workflows from basic clicks to advanced response validation and file operations.