Drive Chrome from Go.

Seven CLIs and an MCP server for browser automation, HAR capture, debugging, and scripted workflows. Single static Go binaries.

Open source. MIT licensed. Used in production by skiff and internal tmc labs tooling.

What it does

Browser automation — cdp CLI for general-purpose Chrome control, inspection, and scripted workflows.
HAR and traffic capture — chrome-to-har and churl for focused capture and browser-backed fetch.
Node and V8 debugging — chdb and ndp attach to Node inspectors for V8 profiling and debugging from the terminal.
CDP scripting — cdpscript and cdpscripttest run and test Chrome DevTools Protocol scripts.
MCP server — exposes browser control as tools any MCP-speaking agent can call.

cdp is where a tmc labs agent reaches the open web. When a skiff agent needs to fetch a page, capture a HAR, or drive a browser session for a task, it speaks MCP to cdp. Separate from axmcp (native macOS) and cove (sandboxed desktop) — different control surfaces for different jobs.

source github.com/tmc/cdp

docs pkg.go.dev/github.com/tmc/cdp

contact tmc@tmc.dev