Ctrlshiftbryan Chrome Devtools Mcp
ctrlshiftbryan-chrome-devtools-mcp is a Claude Code plugin for the Ship phase that exposes Chrome DevTools over MCP for agent-driven debugging, performance analysis, and browser automation.
by ctrlShiftBryan · github.com/ctrlShiftBryan/chrome-devtools-mcp
Connect Chrome DevTools via MCP so Claude can debug pages, inspect network and performance, and automate reliable browser checks with Puppeteer-style control.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install ctrlshiftbryan-chrome-devtools-mcp@ctrlShiftBryan/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:ctrlShiftBryan/chrome-devtools-mcp") and the paste-ready config with skillselion.get_install_config("plugin:ctrlShiftBryan/chrome-devtools-mcp").
What it does
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. Solo builders 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.
Highlights
- 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
Why builders use it
Agents often fix frontend bugs blind because they cannot see live DevTools consoles, network waterfalls, or performance profiles.
Your agent can drive Chrome DevTools via MCP for dependable debugging and performance insight grounded in the actual page.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 3 stars, 0 votes.
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.
Comments
Share how you use ctrlshiftbryan-chrome-devtools-mcp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.