chrome-browser

Configure a dedicated Chrome for Testing environment with CDP on port 9222 for Playwright MCP.

2|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/eins78/agent-skills --skill chrome-browser-eins78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: chrome-browser
Source: https://github.com/eins78/agent-skills/tree/main/skills/chrome-browser
Command: npx skills add https://github.com/eins78/agent-skills --skill chrome-browser-eins78

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npx, and includes scripts (resource) components.

What problem does it solve?

Configure and operate a dedicated CfT Chrome environment to support Playwright MCP with CDP and maintain persistent login sessions, isolating it from daily browser activity to avoid profile conflicts.

Core Features & Use Cases

  • Dedicated Chrome for Testing with CDP accessible at localhost:9222 to enable Playwright MCP automation.
  • Persistent user-data-dir and isolated profile to preserve cookies and logins across restarts.
  • Launchd-based auto-start and multi-session safe operation on macOS for reliable automation workflows.

Quick Start

Install and run the Chrome for Testing setup, then configure Playwright MCP to connect to the CDP endpoint at http://127.0.0.1:9222 and use a persistent profile.

Frequently Asked Questions about chrome-browser

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

FAQPage Schema
How do I use Playwright MCP with a persistent Chrome profile on macOS?

You can use Playwright MCP with a persistent Chrome profile by configuring a dedicated Chrome for Testing environment that exposes CDP on localhost port 9222 and enforces a persistent user-data-dir to maintain login sessions across restarts.

What is Chrome for Testing CDP and why use a dedicated user-data-dir?

Chrome for Testing CDP exposes the Chrome DevTools Protocol on a dedicated port for automation. Using a dedicated user-data-dir isolates your automation profiles from daily browsing activity to avoid profile conflicts and preserve cookies.

Does Playwright MCP require a specific Chrome installation to connect via CDP?

Yes, Playwright MCP requires a stable Chrome for Testing installation configured with appropriate launch flags to expose CDP on port 9222, while avoiding default-browser checks to ensure reliable automated workflows.

How do I auto-start Chrome with CDP on macOS using launchd?

You can auto-start Chrome with CDP on macOS by configuring a launchd-based service that launches the dedicated Chrome for Testing environment with CDP exposure on port 9222, ensuring reliable multi-session automation.

Why does my Playwright MCP connection fail when using my default Chrome profile?

Playwright MCP connections often fail with default profiles due to profile conflicts and missing CDP exposure. Using an isolated Chrome for Testing environment with a dedicated user-data-dir and CDP on port 9222 resolves these issues.