Playwright Server 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 |
|---|---|
| playwright_navigateA | 浏览器导航到指定网址，如果没有活跃的浏览器会话，会自动创建一个新会话 |
| playwright_evaluateC | 在浏览器控制台中执行JavaScript代码并返回执行结果 |
| playwright_get_text_contentB | 获取当前页面中所有可见元素的文本内容，智能过滤重复内容 |
| playwright_get_html_contentC | 获取页面中指定元素的HTML内容 |
| playwright_new_sessionB | 创建新的浏览器会话，打开一个浏览器窗口并可选择性地访问指定网址 |
| playwright_actionC | 根据给定的locator 和action 执行操作 |
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 6 tools
Most tools have distinct purposes: navigation, session creation, HTML/text extraction, JavaScript evaluation, and action execution. However, 'playwright_action' is somewhat broad and could potentially overlap with more specific actions, but descriptions help clarify boundaries.
All tools follow a consistent 'playwright_' prefix with snake_case naming, using descriptive nouns or verbs like 'navigate', 'evaluate', and 'get_html_content'. This pattern is predictable and readable throughout the set.
With 6 tools, this is well-scoped for a Playwright automation server. Each tool serves a clear purpose in browser interaction, from session management to content retrieval, without feeling bloated or insufficient.
The set covers core browser automation tasks like navigation, session handling, and content extraction, but lacks explicit CRUD operations for elements (e.g., create/update/delete) and advanced interactions like waiting or screenshots. Agents can work around this, but notable gaps exist.