Playwright Debug 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_failed_testsB | Get failed tests from a Playwright JSON report |
| analyze_traceB | Analyze a Playwright trace.zip file for a failed test |
| get_network_logC | Get network logs from a Playwright trace.zip file |
| get_action_historyB | Get a chronological list of all actions performed in a Playwright trace |
| get_screenshots_around_timeB | Get screenshots immediately before and after a specific timestamp in the trace |
| suggest_fixC | Suggest a fix for a Playwright test error |
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
Each tool targets a distinct aspect of Playwright debugging: trace analysis, action history, failed tests, network logs, screenshots, and fix suggestions. No two tools have overlapping purposes.
Most tools follow a 'get_' prefix pattern, but 'analyze_trace' and 'suggest_fix' deviate. The naming is largely consistent and readable.
With 6 tools, the server is well-scoped for its debugging purpose—enough to cover key workflows without excess.
Covers core debugging operations on traces and reports. A minor gap is the lack of a tool for replaying traces or getting test logs, but the set is complete for common debugging tasks.