Ctrlshiftbryan Chrome Devtools Mcp
- 3 repo stars
- Updated December 21, 2025
- ctrlShiftBryan/chrome-devtools-mcp
ctrlshiftbryan-chrome-devtools-mcp is a Claude Code plugin that exposes Chrome DevTools over MCP for agent-driven debugging, performance analysis, and browser automation.
About
ctrlshiftbryan-chrome-devtools-mcp wraps Chrome DevTools behind the Model Context Protocol so Claude Code and similar agents can inspect real browser sessions, chase console errors, and reason about performance with the same primitives developers use daily. developers shipping web apps, extensions, or hybrid mobile shells benefit when flaky UI bugs only reproduce in a live tab. The plugin count is one—a dedicated MCP server entry—aimed at automation and in-depth analysis rather than broad marketplace coverage. Place it on Ship testing as the canonical shelf because its triggers align with pre-release verification, regression hunts, and performance tuning; it still helps during Build frontend work when you iterate against a running dev server. Intermediate complexity reflects MCP setup, local Chrome, and safe automation boundaries. Pair it with human judgment on authenticated flows and production data.
- MCP server exposing Chrome DevTools capabilities to coding agents
- Keywords cover debugging, performance, automation, Puppeteer, and in-depth analysis
- Supports reliable browser-driven checks instead of guesswork from static code review
- 1-plugin bundle focused on DevTools—not a full test framework replacement
- Bridges agent reasoning with live page state, console, and network timelines
Ctrlshiftbryan Chrome Devtools Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install ctrlshiftbryan-chrome-devtools-mcp@ctrlShiftBryan/chrome-devtools-mcpAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 3 |
|---|---|
| Last updated | December 21, 2025 |
| Repository | ctrlShiftBryan/chrome-devtools-mcp ↗ |
What it does
Connect Chrome DevTools via MCP so Claude can debug pages, inspect network and performance, and automate reliable browser checks with Puppeteer-style control.
Who is it for?
Web-focused developers who want MCP-backed DevTools and Puppeteer-style automation during test and debug cycles.
Skip if: Backend-only APIs with no browser surface, or teams blocked from running local Chrome automation.
What you get
Your agent can drive Chrome DevTools via MCP for dependable debugging and performance insight grounded in the actual page.
- Running Chrome DevTools MCP server wired to the agent
- Actionable debug traces from live page sessions
- Automated browser checks for regressions and performance hotspots
By the numbers
- 1 plugin in the bundle
- Repository: ctrlShiftBryan/chrome-devtools-mcp
- Keywords include mcp, chrome, devtools, debugging, performance, puppeteer, automation
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
Chrome DevTools MCP integration, not a generic unit-test runner or voice-agent stack.
FAQ
Who is Ctrlshiftbryan Chrome Devtools Mcp for?
Developers using Claude Code who need live Chrome DevTools data and controlled browser automation for web apps and extensions.
When should I use Ctrlshiftbryan Chrome Devtools Mcp?
Use it while testing or debugging frontend issues, performance regressions, and unreliable UI flows before ship.
How do I add Ctrlshiftbryan Chrome Devtools Mcp to my agent?
Install the ctrlShiftBryan/chrome-devtools-mcp Claude Code plugin, configure the MCP server in your agent settings, and ensure Chrome is available for DevTools sessions.