chrome-devtools-mcp

Why we included this project

Chrome DevTools is normally something a human stares at, but this MCP server hands the same inspection powers to a coding agent. Your assistant can drive a live browser through it: clicking elements, reading network requests, taking screenshots, and pulling console errors with source-mapped stack traces, so it stops guessing about what the page actually shows. The performance tooling records traces and returns concrete insights, which matters when you are chasing slow renders or layout shifts in a real browser. Because automation runs through Puppeteer and waits for action results, it holds up better than scripted clicks that fire and hope. If you use Claude, Cursor, Copilot, or Antigravity, this is a straightforward way to give the agent hands-on browser access for testing and debugging.