Bach Ai Tools Chrome Devtools Mcp
bach-ai-tools-chrome-devtools-mcp is a Claude Code plugin for the Ship phase that connects your agent to Chrome DevTools over MCP for debugging, automation, and performance analysis.
by BACH-AI-Tools · github.com/BACH-AI-Tools/chrome-devtools-mcp
Give Claude Code reliable browser debugging, automation, and performance signals from real Chrome sessions instead of guessing from static code.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install bach-ai-tools-chrome-devtools-mcp@BACH-AI-Tools/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:BACH-AI-Tools/chrome-devtools-mcp") and the paste-ready config with skillselion.get_install_config("plugin:BACH-AI-Tools/chrome-devtools-mcp").
What it does
bach-ai-tools-chrome-devtools-mcp is a Claude Code plugin that exposes an MCP server wired to Chrome DevTools so your agent can drive a real browser, inspect DOM and network behavior, and reason about performance problems with evidence. Solo builders shipping web apps, browser extensions, or marketing sites use it when screenshots and source alone are not enough to explain slow loads, flaky interactions, or layout bugs. Install it during Ship when you are profiling before launch or chasing regressions after a deploy. It complements generic coding skills by adding live browser telemetry rather than replacing your test framework. Expect Node or MCP host setup and a Chrome-capable environment; the payoff is faster root-cause analysis on frontend issues without constant manual DevTools tab switching.
Highlights
- MCP bridge to Chrome DevTools for in-depth page inspection and debugging
- Performance and reliability analysis via Puppeteer-style automation keywords
- Supports automation workflows for reproducing UI issues in the agent loop
- Single-plugin bundle focused on Chrome + MCP integration
Why builders use it
Agents cannot see what actually happens in the browser, so frontend bugs and perf regressions stall on manual DevTools work.
After you register the MCP server, Claude can inspect live Chrome sessions and ground fixes in real runtime data instead of assumptions.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is bach-ai-tools-chrome-devtools-mcp for?
Solo and small-team builders using Claude Code on web frontends who need DevTools-level visibility during debug and perf passes.
When should I use bach-ai-tools-chrome-devtools-mcp?
Use it in Ship when profiling page load, tracing flaky UI, or validating fixes against a real Chrome instance before or after deploy.
How do I add bach-ai-tools-chrome-devtools-mcp to my agent?
Add the plugin from the BACH-AI-Tools/chrome-devtools-mcp repo in Claude Code, configure the MCP server entry, and ensure Chrome is available on the machine running the tools.
Comments
Share how you use bach-ai-tools-chrome-devtools-mcp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.