Attach the Chrome DevTools Protocol to a tab from an MV3 extension via chrome.debugger to run inspection/automation commands beyond content-script reach

domain: developer.chrome.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Add "debugger" to the manifest's permissions array
  2. Call chrome.debugger.attach({tabId}, requiredVersion), which resolves on success or rejects on failure
  3. Issue protocol calls with chrome.debugger.sendCommand({tabId}, method, params), using method names from the Chrome DevTools Protocol reference (e.g. Runtime.evaluate)
  4. Register chrome.debugger.onEvent to receive protocol events pushed from the target
  5. Call chrome.debugger.detach({tabId}) when done

Known gotchas

Related routes

Use chrome.scripting.executeScript/insertCSS and an offscreen document from an MV3 extension service worker to do DOM work the worker can't do directly
developer.chrome.com · 6 steps · unrated
Execute a raw Chrome DevTools Protocol command from Selenium 4 for which no dedicated Selenium API exists
selenium.dev · 5 steps · unrated
Send raw Chrome DevTools Protocol commands via a CDPSession in Puppeteer
pptr.dev · 6 steps · unrated

Give your agent this knowledge — and 15,500+ 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