browser_cdp

Connect to and control Chrome browsers via the Chrome DevTools Protocol.

839|277|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/matevip/mateclaw --skill browser-cdp-matevip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser_cdp
Source: https://github.com/matevip/mateclaw/tree/main/mateclaw-server/src/main/resources/skills/browser_cdp
Command: npx skills add https://github.com/matevip/mateclaw --skill browser-cdp-matevip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables remote debugging and multi-tool sharing of a live Chrome session by connecting through the Chrome DevTools Protocol (CDP). It can attach to an already-running browser, scan local CDP ports, or start a Chrome instance with a fixed CDP port to ensure a stable, shareable session for multiple tools or agents.

Core Features & Use Cases

  • Connect to an existing Chrome instance via CDP and perform standard browser actions (open, snapshot, click, type).
  • Scan the local machine to discover available CDP ports for quick attachment.
  • Start Chrome with a fixed CDP port to guarantee a deterministic session that can be shared across tools.
  • Enable collaboration across multiple agents by routing commands to the same browser instance.
  • Safety and separation: stop only disconnects from the browser, preserving the user’s Chrome process.

Quick Start

Connect to a running Chrome via CDP or launch Chrome with a fixed CDP port to enable shared browser access.

Frequently Asked Questions about browser_cdp

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

FAQPage Schema
How do I connect to a running Chrome instance via CDP for remote debugging?

Connect to a running Chrome instance via CDP by scanning local ports to discover available sessions or attaching directly to an existing browser. This enables remote debugging and shared multi-tool access to the live session.

Can multiple agents share the same Chrome session over CDP?

Multiple agents can share the same Chrome session over CDP by routing commands to a single browser instance. Starting Chrome with a fixed CDP port guarantees a deterministic, shareable session for multi-agent collaboration.

How do I start Chrome with a fixed CDP port for automation workflows?

Start Chrome with a fixed CDP port to guarantee a deterministic session that can be shared across tools. This approach ensures a stable connection for multi-agent automation and debugging workflows.

Does stopping the CDP connection close my external Chrome process?

Stopping the CDP connection does not close your external Chrome process. The stop action only disconnects from the browser, preserving the user's Chrome instance and ensuring safe separation.

What tools do I need to control a Chrome session through the DevTools Protocol?

Controlling a Chrome session through the DevTools Protocol requires the browser_use and execute_shell_command tools as dependencies. These enable standard browser actions like opening, snapshotting, clicking, and typing.

How do I discover available CDP ports on my local machine?

Discover available CDP ports on your local machine by scanning the system for active remote-debugging endpoints. This allows quick attachment to an already-running Chrome browser without manual port configuration.