actor
Playwright-powered MCP browser automation server
Install & Use
Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:
Help me install this AI Skill: actor. It is used for: Playwright-powered MCP browser automation server Full Skill content: https://321skill.com/skills/actor/raw/index.md Read that page and install it.
The prompt includes a link to the full Skill content. You can also view the full content.
This Skill addresses the issue of AI's inability to directly operate browsers and extract structured data from web pages. Traditional browser automation either relies on screenshots and vision models (costly and slow) or requires complex DOM selectors. In contrast, Playwright MCP provides purely structured page interaction via the Accessibility Tree, enabling LLMs to accurately click, fill forms, and extract data without needing to interpret pixels.
Usage is straightforward: simply configure the server URL and Apify Token in your MCP client (e.g., Claude Desktop, Cursor). You can then use natural language instructions to have the AI perform browser actions, such as "Open Baidu's homepage, search for 'Playwright', click the first result, and extract the page title and summary." Under the hood, instructions are automatically mapped to Playwright tools like browser_click and browser_navigate, returning structured snapshots.
It is ideal for teams or individuals who frequently perform web scraping, automated testing, or form filling. Particularly for developers already using the MCP ecosystem, it provides browser control capabilities without additional learning. For scenarios like e-commerce operations, competitive analysis, and data collection, this Skill can significantly reduce manual effort.
We recommend using this tool for structured data extraction (e.g., tables, lists) to avoid the high latency and token waste associated with screenshot-based methods. Note that it primarily relies on Playwright's Accessibility Tree; for pages with heavy JavaScript rendering or many custom components, it may not fully capture all interactive elements. In such cases, it can be supplemented with screenshot tools.
Key Features
Unlike screenshot-based browser MCPs (e.g., browser-use), it utilizes Playwright's Accessibility Tree instead of pixel input, eliminating the need for vision models. This results in faster execution, lower token consumption, and deterministic operation outcomes.
Limitations
Requires Node.js 18+ environment and depends on an Apify platform Token (free tier has request limits). Coverage for highly dynamic web components (e.g., Shadow DOM) may be incomplete.
FAQ
What dependencies need to be installed?
No local installation is required; simply configure your MCP client to connect to the remote server. For self-hosting, clone the repository and run `npm install && npm start`.
What browser operations are supported?
Core operations such as clicking, inputting, navigating, scrolling, taking screenshots, and retrieving console messages are supported. See the tool list for specifics (e.g., `browser_click`, `browser_navigate`, `browser_snapshot`).
Installation guide for AI assistants
If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:
Visit https://321skill.com/skills/actor/raw/index.md to read the original Skill definition (Markdown format) for actor, and install it according to the instructions.
Raw Markdown URL for AI: /skills/actor/raw/index.md