MCP Playwright CDP
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 |
|---|---|
| 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_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_evaluateC | Execute JavaScript in the browser console |
| 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Browser console logs |
TDQS
Scored across 12 tools
Most tools have distinct purposes, but there is some overlap between playwright_click and playwright_select as both interact with page elements, which could cause minor confusion. The HTTP methods (GET, POST, PUT, PATCH, DELETE) are clearly differentiated, and other tools like playwright_navigate, playwright_screenshot, and playwright_evaluate have unique functions.
All tool names follow a consistent 'playwright_' prefix with a verb or action (e.g., click, get, navigate), using snake_case uniformly. This predictable pattern makes it easy for agents to understand and navigate the tool set without naming conflicts or style variations.
With 12 tools, the count is well-scoped for a Playwright CDP server, covering essential web automation tasks like navigation, interaction, HTTP requests, and debugging. Each tool serves a specific purpose, avoiding bloat while providing comprehensive functionality for the domain.
The tool set covers key areas: navigation, element interaction, HTTP methods, and debugging (screenshot, evaluate). Minor gaps exist, such as missing tools for handling cookies, waiting for elements, or managing browser contexts, but core workflows are well-supported, allowing agents to perform most common automation tasks.