Cloudflare Playwright MCP
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 |
|---|---|
| init-browserC | Initialize a browser with a URL |
| get-full-domA | Get the full DOM of the current page. (Deprecated, use get-context instead) |
| get-screenshotB | Get a screenshot of the current page |
| execute-codeA | Execute custom Playwright JS code against the current page |
| get-interactive-snapshotB | Get a snapshot focused on interactive elements (buttons, links, inputs) with annotated screenshot for UI automation |
| get-full-snapshotB | Get a complete snapshot of the page including all visible content (text, images, forms, etc.) for understanding the full context |
| get-text-snapshotB | Get all text content from the page (headings, paragraphs, lists) for reading and content extraction |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| server-flow | Get prompt on how to use this MCP server |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have distinct purposes, with clear separation between code execution, DOM/snapshot retrieval, and browser initialization. However, get-full-dom and get-context (implied by deprecation note) could cause confusion, and the various snapshot tools (full, interactive, text) might overlap slightly in content extraction scenarios.
All tool names follow a consistent verb-object pattern with hyphen separation (e.g., execute-code, get-screenshot, init-browser). The naming is predictable and readable throughout the set, with no mixing of conventions.
With 7 tools, this server is well-scoped for Playwright automation, covering core operations like browser setup, code execution, and various snapshot types. Each tool serves a clear purpose without bloat, making it manageable and functional.
The toolset covers essential Playwright workflows: initialization, code execution, and multiple snapshot types for different contexts. A minor gap exists in navigation or page interaction tools (e.g., click, type), but agents can work around this using execute-code for custom actions.