Playwright MCP Server
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
The tools have overlapping purposes that could cause confusion, particularly around snapshot variants (get-full-snapshot, get-interactive-snapshot, get-text-snapshot) which all extract page content in different ways. However, descriptions help differentiate them by specifying focus areas like interactive elements or text content, preventing complete misselection.
Tool names follow a consistent verb-object pattern with hyphens (e.g., execute-code, get-screenshot), making them predictable and readable. The only minor deviation is 'init-browser' which uses 'init' instead of a more standard verb like 'launch' or 'open', but it still fits the overall naming convention.
With 7 tools, this server is well-scoped for browser automation with Playwright, covering key operations like initialization, code execution, and various content extraction methods. Each tool earns its place by addressing distinct aspects of web interaction without being overly sparse or bloated.
The toolset provides solid coverage for core Playwright workflows, including browser setup, DOM/content access, and automation execution. A minor gap exists in navigation control (e.g., no explicit 'navigate' or 'go-back' tools), but agents can work around this using execute-code or init-browser with URLs.