playwright-browser-install

To install the Playwright browser defined in config, run this when the browser is missing or not installed.

⭐6stars🔀3forks📁View on GitHub🕐Updated Jan 7, 2026

When & Why to Use This Skill

The playwright-browser-install skill automates the essential setup of browser environments required for web automation and scraping. It detects missing browser binaries and installs the specific versions defined in the configuration, ensuring that Playwright-based agents can execute tasks without manual environment configuration or 'browser not found' errors.

Use Cases

  • Automated Environment Provisioning: Seamlessly installing necessary browser engines (Chromium, Firefox, or WebKit) when setting up a new web automation agent or workspace.
  • Self-Healing Workflows: Automatically triggering a browser installation when a runtime error indicates that the required browser is missing, ensuring workflow continuity.
  • DevOps & CI/CD Integration: Streamlining the preparation of ephemeral testing environments by ensuring all browser dependencies are correctly installed before running automated web tests.
nameplaywright-browser-install
description"To install the Playwright browser defined in config, run this when the browser is missing or not installed."

Usage

Use the MCP tool dev-swarm.request to send the payload as a JSON string:

{"server_id":"playwright","tool_name":"browser_install","arguments":{}}

Tool Description

Install the browser specified in the config. Call this if you get an error about the browser not being installed.

Arguments Schema

The schema below describes the arguments object in the request payload.

{
  "type": "object",
  "properties": {},
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Background Tasks

If the tool returns a task id, poll the task status via the MCP request tool:

{"server_id":"playwright","method":"tasks/status","params":{"task_id":"<task_id>"}}