Open source✓ Confirmed in official docsAdded Nov 15
How to connect Chrome DevTools MCP to Claude Code and Codex for real-browser debugging
Chrome DevTools MCP (chrome-devtools-mcp) is an MCP server and CLI from the Chrome DevTools team. It lets Claude Code or Codex launch a real Chrome, drive pages, and read network requests, console messages and performance traces directly.
- You need a Node.js LTS release and current stable Chrome. In Claude Code, one command adds it for every project.
claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest
For Codex:
codex mcp add chrome-devtools -- npx chrome-devtools-mcp@latest
- To get the debugging skills too, install it as a plugin inside Claude Code instead. If you already added the MCP server with the command above, remove it first. Restart Claude Code afterwards and check with
/skills.
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
/plugin install chrome-devtools-mcp@chrome-devtools-plugins
- Check the connection with this first prompt. If the agent opens Chrome and records a performance trace, it works. The browser starts when the agent first uses a tool that needs it, not when the server connects.
Check the performance of https://developers.chrome.com
The agent can read and change anything open in that Chrome, so keep personal data out of it. Google collects usage statistics by default; opt out with the --no-usage-statistics flag, and stop performance tools from sending trace URLs to the CrUX API with --no-performance-crux. Only Google Chrome and Chrome for Testing are officially supported.
Sources
Get notified when a new tip lands
Tip alerts only go out in the app. Install it and turn notifications on.