playwright-mcp-skill

Automate browser tasks via Playwright MCP over UXC stdio.

31|8|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/citedy/adclaw --skill playwright-mcp-skill-citedy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: playwright-mcp-skill
Source: https://github.com/citedy/adclaw/tree/main/src/adclaw/agents/skills/playwright-mcp
Command: npx skills add https://github.com/citedy/adclaw --skill playwright-mcp-skill-citedy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Enable deterministic browser automation by orchestrating Playwright MCP tasks over UXC stdio, reducing manual scripting and brittle ad-hoc interactions.

Core Features & Use Cases

  • Deterministic navigation, DOM snapshots, and scripted interactions via fixed stdio endpoints.
  • Daemon-friendly session reuse with safety guardrails for predictable automation.
  • Use cases include automated web testing, data collection, UI automation, and end-to-end flows invoked from the CLI.

Quick Start

Use the fixed stdio endpoint to run Playwright MCP commands from the CLI.

Frequently Asked Questions about playwright-mcp-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser tasks with Playwright MCP from the command line?

Automating browser tasks with Playwright MCP involves executing deterministic page navigation, DOM snapshots, and scripted interactions via a fixed stdio endpoint from your CLI. This setup provides controlled environment execution and enforces safety guardrails for predictable automation.

What is Playwright MCP over UXC stdio used for?

Playwright MCP over UXC stdio is used for deterministic browser automation, reducing manual scripting and brittle ad-hoc interactions. It orchestrates tasks like automated web testing, data collection, and end-to-end UI flows directly from the command line.

Do I need a specific Node and Playwright setup to run Playwright MCP commands?

Yes, running Playwright MCP commands requires a properly configured Node, Playwright, and MCP setup. You must use the fixed stdio endpoint to execute these deterministic browser automation scripts in your controlled environment.

Does Playwright MCP support daemon-friendly session reuse for automated web testing?

Yes, Playwright MCP supports daemon-friendly session reuse for automated web testing. It includes built-in safety guardrails to ensure predictable automation and deterministic interactions during your CLI-invoked end-to-end flows.

What are the limitations of using a fixed stdio endpoint for browser automation?

The fixed stdio endpoint limits browser automation to controlled environments, enforcing strict guardrails for predictable execution. It focuses on deterministic scripted interactions rather than dynamic or ad-hoc exploratory browser tasks.