playwright-report-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PW_ALLOWED_DIRS | No | path.delimiter-separated list of directories the workingDirectory parameter may point at. | . |
| PW_RESULTS_FILE | No | Absolute path to the JSON reporter output file. | <workingDirectory>/test-results/results.json |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_testsC | Run Playwright tests and return structured results. |
| get_run_statusA | Return status for a tracked Playwright run. Pass runId for a specific background run, or omit it to inspect the latest tracked run for a workingDirectory. If no tracked run exists, returns idle with current results.json metadata; it does not inspect unrelated OS processes. |
| get_failed_testsA | Return failed tests from the last run with error messages and attachment paths. |
| get_test_attachmentA | Read the content of a named attachment for a specific test from the last run. |
| list_testsA | List all tests with their spec file and tags without running them. |
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 5 tools
Each tool has a clear, non-overlapping purpose: running tests, listing tests, retrieving failures, checking run status, and reading attachments. No two tools could be easily confused.
All tool names follow a consistent verb_noun pattern (run_tests, list_tests, get_failed_tests, get_run_status, get_test_attachment). The verbs are clear and the pattern is uniform across the set.
With 5 tools, the server is well-scoped for its purpose of managing Playwright test runs and reports. Each tool covers a distinct aspect without unnecessary bloat or thinness.
The tool surface covers the core tasks: running, listing, inspecting failures, checking status, and reading attachments. A minor gap is the lack of a way to retrieve all test results (not just failures), but the current set handles the primary workflow effectively.