Chromedevtools Chrome Devtools Mcp
- 47.7k repo stars
- Updated July 27, 2026
- ChromeDevTools/chrome-devtools-mcp
Chrome DevTools MCP is a Claude Code plugin that exposes Chrome DevTools debugging, performance analysis, and browser automation to coding agents via MCP.
About
Chrome DevTools MCP (ChromeDevTools/chrome-devtools-mcp) is a Claude Code–compatible plugin packaging an MCP server that connects coding agents to Chrome DevTools. developers 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.
- 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
Chromedevtools Chrome Devtools Mcp by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin install chromedevtools-chrome-devtools-mcp@ChromeDevTools/chrome-devtools-mcpAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 47.7k |
|---|---|
| Last updated | July 27, 2026 |
| Repository | ChromeDevTools/chrome-devtools-mcp ↗ |
What it does
Register Chrome DevTools MCP so your coding agent can debug, automate, and analyze performance in Chrome with reliable DevTools and Puppeteer-style control.
Who is it for?
Best when you're shipping web or extension frontends and want agent-driven Chrome debugging without leaving the Claude Code or MCP workflow.
Skip if: Pure backend or CLI projects with no browser surface, or developers who cannot run Chrome/Chromium locally.
What you get
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.
- MCP-accessible Chrome DevTools debugging and inspection
- Agent-driven browser automation for repro steps
- Performance and network analysis hooks for pre-ship checks
By the numbers
- Repository ChromeDevTools/chrome-devtools-mcp lists pluginCount: 1
- Plugin keywords include mcp, devtools, debugging, performance, and puppeteer
Recommended Plugins
0xbigboss Linear CliLinear CLI built with Zig1
15195999826 LomomarketplaceLomo's Claude Code Plugin Marketplace1
1broseidon MarketplaceCurated collection of Claude Code plugins for fullstack development teams1
4rgon4ut Cc Zig LspZig LSP plugin for Claude Code4
708u TwigSimplify git worktree and branch management with configurable symlinks, change carrying, and cleanup.22
8avalon8 AvalonclaudemarketAvalon 的 Claude Code 插件市场How it compares
Browser DevTools MCP integration, not a spec-driven productivity plugin or session memory layer.
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.