Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.oguzc/playwright-wizard-mcp

NPM · PLAYWRIGHT-WIZARD-MCP · SCANNED SEP 20

MCP server providing Playwright test generation wizard with intelligent prompts and best practices

−1 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency69
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to oguzc/playwright-wizard-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 343 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 634 tokens (~42/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.oguzc/playwright-wizard-mcp server?

io.github.oguzc/playwright-wizard-mcp runs locally as an npm package, launched with npx -y playwright-wizard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · playwright-wizard-mcp

# add to Claude Code
claude mcp add oguzc-playwright-wizard-mcp -- npx -y playwright-wizard-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "oguzc-playwright-wizard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-wizard-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "oguzc-playwright-wizard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-wizard-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add oguzc-playwright-wizard-mcp -- npx -y playwright-wizard-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "oguzc-playwright-wizard-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "playwright-wizard-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add oguzc-playwright-wizard-mcp --command npx --arg -y --arg playwright-wizard-mcp
# ~/.hermes/config.yaml
mcp_servers:
  oguzc-playwright-wizard-mcp:
    command: "npx"
    args: ["-y", "playwright-wizard-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "oguzc-playwright-wizard-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "playwright-wizard-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add oguzc-playwright-wizard-mcp -t stdio -c npx -a -y playwright-wizard-mcp
// mcp.json
{
  "mcpServers": {
    "oguzc-playwright-wizard-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "playwright-wizard-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: unverified → fail functional
  • 13 Sept 26 +1
    • Security disclosure: fail → unverified functional
  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.83 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/playwright-wizard-mcp@0.1.6

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo oguzc/playwright-wizard-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/oguzc/playwright-wizard-mcp/.github/workflows/publish.yml@refs/tags/v0.1.6
Rekor log index 601060843
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:9dd9cbfe608427dc99da60676c80d3979d9ef9ba9e27aafbfdbe8d47d4d80a09442aa5fe22d045d643ceedf3adc28ae1393bdfa575928c3c27e877c9f

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 15 exposed · ~634 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add-accessibility ~52

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

add-api-testing ~51

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

advanced-optimization ~32

Optional: Advanced optimization - deep dive into performance optimization, auth state reuse, parallel configuration tuning, and advanced patterns

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

analyze-app ~69

⚠️ 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)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate-page-objects ~57

⚠️ 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)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate-test-plan ~56

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

implement-test-suite ~58

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-core-principles ~26

Get core testing principles and quality standards that guide all Playwright test implementations

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-data-storage-patterns ~30

Get data storage patterns for test infrastructure (ORM, JSON files, in-memory, MSW)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-fixture-patterns ~27

Get Playwright fixture patterns for parallel execution, state management, and test isolation

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-mcp-setup ~24

Get MCP server setup instructions and usage patterns for Playwright Wizard

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-selector-strategies ~28

Get selector strategies, HTML quality scoring guidelines, and best practices for robust element selection

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reference-workflow-overview ~25

Get high-level workflow guide explaining the test creation process and prompt relationships

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

setup-ci-cd ~48

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

setup-infrastructure ~51

⚠️ 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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.oguzc/playwright-wizard-mcp server?

io.github.oguzc/playwright-wizard-mcp is listed in the public MCP registry as io.github.oguzc/playwright-wizard-mcp. MCP server providing Playwright test generation wizard with intelligent prompts and best practices. This page covers its npm package (playwright-wizard-mcp).

Is the io.github.oguzc/playwright-wizard-mcp server safe to use?

io.github.oguzc/playwright-wizard-mcp scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.oguzc/playwright-wizard-mcp server expose?

io.github.oguzc/playwright-wizard-mcp exposes 15 tools: analyze-app, generate-test-plan, setup-infrastructure, generate-page-objects, implement-test-suite, and 10 more. Their descriptions and schemas cost roughly 634 tokens of context every time the server is loaded.

Is the io.github.oguzc/playwright-wizard-mcp server still maintained?

io.github.oguzc/playwright-wizard-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.oguzc/playwright-wizard-mcp server under?

io.github.oguzc/playwright-wizard-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.