MCP Server - Test Migration (WDIO to Playwright)
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_wdio_testA | Analyzes a WebDriverIO test file using AST parsing and extracts detailed information about its structure, selectors, commands, and dependencies. Detects if test is already partially migrated to Playwright. |
| migrate_to_playwrightA | Migrates a WebDriverIO test to Playwright syntax using AST transformation. Supports partial migrations and preserves already-migrated code. Uses modern Playwright locators (getByRole, getByLabel, getByTestId with data-test-id). Supports TypeScript output. |
| refactor_to_pomA | Refactors a migrated Playwright test to use Page Object Model pattern. Extracts actual selectors and creates proper page object classes with methods. |
| get_playwright_docsC | Retrieves relevant Playwright documentation for specific features, commands, or concepts. Useful for understanding migration patterns. |
| compare_frameworksB | Compares WDIO and Playwright commands/concepts side by side. Helps understand equivalent functionality. |
| detect_project_stateA | Analyzes project structure to detect existing Playwright configuration, migrated tests, page objects, and WDIO setup. Helps understand current migration state. |
| migrate_configB | Migrates wdio.conf.js to playwright.config.ts. Preserves existing Playwright config if present. |
| register_custom_commandsB | Registers custom WDIO commands with their Playwright equivalents for migration. Allows handling project-specific custom commands. |
| generate_migration_reportB | Generates a comprehensive migration report as a markdown file. Includes test files, tags, migration status, and statistics. |
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 9 tools
Each tool has a distinct, well-defined purpose within the migration workflow, with no overlap or ambiguity. For example, analyze_wdio_test focuses on test analysis, migrate_to_playwright handles syntax conversion, and refactor_to_pom deals with architectural refactoring, ensuring clear boundaries.
All tools follow a consistent verb_noun naming pattern (e.g., analyze_wdio_test, generate_migration_report, migrate_config). The naming is uniform, readable, and predictable across all nine tools, with no deviations in style or convention.
With 9 tools, the server is well-scoped for its purpose of migrating from WDIO to Playwright. Each tool earns its place by covering different aspects of the migration process, from analysis and comparison to actual migration and refactoring, without being overly sparse or bloated.
The tool set provides complete coverage of the migration domain, including analysis (analyze_wdio_test, detect_project_state), comparison (compare_frameworks), migration (migrate_to_playwright, migrate_config), refactoring (refactor_to_pom), documentation (get_playwright_docs), reporting (generate_migration_report), and customization (register_custom_commands). No obvious gaps exist, supporting end-to-end workflows.