Chromedevtools Chrome Devtools Mcp
Chrome DevTools MCP is a Claude Code plugin for the Ship phase that exposes Chrome DevTools debugging, performance analysis, and browser automation to coding agents via MCP.
by ChromeDevTools · github.com/ChromeDevTools/chrome-devtools-mcp
Register Chrome DevTools MCP so your coding agent can debug, automate, and analyze performance in Chrome with reliable DevTools and Puppeteer-style control.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install chromedevtools-chrome-devtools-mcp@ChromeDevTools/chrome-devtools-mcpBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:ChromeDevTools/chrome-devtools-mcp") and the paste-ready config with skillselion.get_install_config("plugin:ChromeDevTools/chrome-devtools-mcp").
What it does
Chrome DevTools MCP (ChromeDevTools/chrome-devtools-mcp) is a Claude Code–compatible plugin packaging an MCP server that connects coding agents to Chrome DevTools. Solo builders shipping web apps gain agent-accessible debugging, performance analysis, and browser automation instead of manually copying console errors into chat. The README positions it as DevTools for coding agents with emphasis on reliable, in-depth inspection rather than shallow page fetches. Skillselion tags it multi-phase: primary Ship → testing for pre-release diagnosis, with secondary Build → frontend when iterating on UI. It is a Development Tools integration, not a product-management methodology. You typically need Node, an MCP-capable agent, and a Chromium/Chrome environment. Pair it with your usual test and review flow when client-side bugs or Core Web Vitals block ship confidence.
Highlights
- MCP bridge exposing Chrome DevTools capabilities to coding agents
- In-depth debugging and performance analysis beyond screenshot-only browser tools
- Automation patterns using Puppeteer-related reliability keywords from the repo
- Suited for frontend verification, network inspection, and deep diagnostics
- Single-plugin listing from ChromeDevTools/chrome-devtools-mcp
Why builders use it
Agents cannot see real browser DevTools data, so frontend bugs, network failures, and performance regressions stall behind vague descriptions and guesswork.
After you connect the MCP plugin, your agent can drive Chrome DevTools-backed inspection and automation so you fix UI and performance issues with evidence before you ship.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 33.4k stars, 0 votes.
FAQ
Who is chromedevtools-chrome-devtools-mcp for?
It is for developers using MCP-enabled agents who need Chrome DevTools-level debugging, performance insight, and automation on web apps.
When should I use chromedevtools-chrome-devtools-mcp?
Use it during frontend implementation and pre-ship testing when console errors, network calls, or performance traces require real browser instrumentation.
How do I add chromedevtools-chrome-devtools-mcp to my agent?
Install the plugin from ChromeDevTools/chrome-devtools-mcp, configure the MCP server in Claude Code or your agent’s MCP settings, and ensure Chrome or Chromium is available for DevTools sessions.
Comments
Share how you use chromedevtools-chrome-devtools-mcp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.