Attach to a Chrome instance using the Chrome DevTools MCP server for CDP-over-MCP tool access

domain: github.com/ChromeDevTools/devtools-mcp · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Launch Chrome with remote debugging enabled: google-chrome --remote-debugging-port=9222 --no-first-run --no-default-browser-check
  2. Install and start the Chrome DevTools MCP server: npx @chrome-devtools/mcp --port=9222
  3. Register the MCP server in your agent or MCP client config pointing to its stdio or SSE endpoint
  4. The server exposes CDP domain tools (Network, Runtime, DOM, Debugger) as MCP tools the LLM can call
  5. Use the Runtime.evaluate tool to execute JavaScript in the page context and retrieve return values
  6. Use the Network.enable + Network.responseReceived tools to stream network events to the agent for analysis

Known gotchas

Related routes

Attach the Chrome DevTools Protocol to a tab from an MV3 extension via chrome.debugger to run inspection/automation commands beyond content-script reach
developer.chrome.com · 5 steps · unrated
Send raw Chrome DevTools Protocol commands via a CDPSession in Puppeteer
pptr.dev · 6 steps · unrated
Drive headless Chrome directly via the Chrome DevTools Protocol (CDP) without a high-level browser automation library
chromedevtools.github.io · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans