Playwright Wizard 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 |
|---|---|
| analyze-appA | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Step 1: Analyze the application - detect tech stack from package.json, browse pages using Playwright MCP, evaluate DOM quality, and create test strategy files (project-config.md, pages.md, selector-strategy.md) |
| generate-test-planC | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Step 2: Generate test plan - create detailed test scenarios with user flows, edge cases, acceptance criteria, and test data based on the analysis |
| setup-infrastructureA | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Step 3: Setup infrastructure - create Playwright config, fixtures for parallel execution, test helpers, and proper folder structure |
| generate-page-objectsC | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Step 4: Generate page objects - create type-safe page object models with optimal selectors (getByRole/Label preferred, test IDs when needed) |
| implement-test-suiteB | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Step 5: Implement & verify tests - write complete test suite using page objects, with proper assertions, error handling, parallel execution verification, and performance optimization |
| setup-ci-cdB | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Optional: Setup CI/CD - add GitHub Actions workflow for automated testing with parallel execution and artifact reporting |
| add-accessibilityC | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Optional: Add accessibility testing - integrate axe-core, add WCAG 2.1 AA compliance checks, and test keyboard navigation |
| add-api-testingC | ⚠️ CALL THIS TOOL IMMEDIATELY to get full workflow instructions. Optional: Add API testing - test REST/GraphQL/tRPC APIs with request/response validation and integration with UI tests |
| advanced-optimizationC | Optional: Advanced optimization - deep dive into performance optimization, auth state reuse, parallel configuration tuning, and advanced patterns |
| reference-core-principlesA | Get core testing principles and quality standards that guide all Playwright test implementations |
| reference-workflow-overviewA | Get high-level workflow guide explaining the test creation process and prompt relationships |
| reference-mcp-setupA | Get MCP server setup instructions and usage patterns for Playwright Wizard |
| reference-selector-strategiesA | Get selector strategies, HTML quality scoring guidelines, and best practices for robust element selection |
| reference-fixture-patternsA | Get Playwright fixture patterns for parallel execution, state management, and test isolation |
| reference-data-storage-patternsA | Get data storage patterns for test infrastructure (ORM, JSON files, in-memory, MSW) |
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 15 tools
Each tool has a distinct role within the workflow: analyze, plan, setup, generate page objects, implement, plus separate reference tools and optional add-ons. The numbered steps (Step 1-5) further clarify the intended sequence, eliminating ambiguity.
Tool names consistently use a verb_noun pattern with prefixes like 'analyze-', 'generate-', 'setup-', 'reference-', and 'add-'. The only minor deviation is 'advanced-optimization' but it still fits the pattern of optional additions.
With 15 tools, the server covers a full test creation workflow (5 steps), essential reference materials (6), and optional enhancements (4). The count is well-scoped for its purpose, neither excessive nor insufficient.
The tool set covers the complete lifecycle from app analysis to test implementation, including infrastructure setup, page objects, and references. Optional tools add accessibility, API testing, optimization, and CI/CD, leaving no obvious gaps.