Chrome DevTools MCP
Let your coding agent inspect, debug, and profile live Chrome sessions through MCP instead of guessing from screenshots alone.
Overview
Chrome DevTools MCP is a MCP server for the Ship phase that connects AI agents to Chrome DevTools for live browser inspection and debugging.
What is this MCP server?
- stdio MCP transport via npm package @dinesh-nalla-se/chrome-devtools-mcp (server version 0.10.2)
- Chrome DevTools protocol bridge for agent-driven browser inspection and debugging
- Published on GitHub at dinesh-nalla-se/chrome-devtools-mcp with MCP server.schema.json metadata
- Fits Claude Code, Cursor, and other MCP clients that need real browser context
- Complements Playwright-style automation with deep DevTools-level control
- Server version 0.10.2 on npm identifier @dinesh-nalla-se/chrome-devtools-mcp
- stdio transport per MCP server.schema.json (2025-10-17)
- GitHub source: github.com/dinesh-nalla-se/chrome-devtools-mcp
What problem does it solve?
Agents cannot see what is actually happening in the browser, so frontend bugs turn into slow guess-and-check loops.
Who is it for?
Solo builders debugging production-like Chrome sessions with Claude Code or Cursor during test-and-fix cycles.
Skip if: Teams that only need static code review with no browser runtime, or workflows blocked from running Chrome locally.
What do I get? / Deliverables
After you register the server, your agent can pull DevTools-grounded signals while you fix UI, network, and performance issues faster.
- Registered Chrome DevTools MCP server in your agent config
- Agent-accessible browser inspection and debugging during test sessions
Recommended MCP Servers
Journey fit
Browser verification and debugging sit in Ship so agents can reproduce UI issues and performance problems before release. Testing is the canonical shelf because DevTools access supports DOM inspection, network traces, and console debugging during QA loops.
How it compares
MCP browser integration via DevTools, not a standalone code-review or planning skill.
Common Questions / FAQ
Who is Chrome DevTools MCP for?
It is for indie developers and agent users who ship web UIs and want MCP tools that read real Chrome DevTools state.
When should I use Chrome DevTools MCP?
Use it in Ship/testing when you need DOM, console, or network evidence while an agent helps reproduce and fix browser bugs.
How do I add Chrome DevTools MCP to my agent?
Add the npm stdio server @dinesh-nalla-se/chrome-devtools-mcp to your MCP client config and ensure Chrome is available on the machine running the agent.