Chrome DevTools MCP connects an MCP-compatible agent to a live Chrome browser for debugging, automation, and performance work. It exposes Chrome DevTools capabilities through MCP, so agents can inspect network traffic, collect traces, capture screenshots, and automate browser actions from the same server.
Installs into .claude/skills of the current project.
Are you the author of Chrome Devtools Mcp Browser Debugging Performance Analysis?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/agentskillexchange-chrome-devtools-mcp-browser-debugging-performance-)
---
name: "Chrome DevTools MCP Browser Debugging and Performance Analysis"
slug: "chrome-devtools-mcp-browser-debugging-performance-analysis"
description: "Chrome DevTools MCP connects an MCP-compatible agent to a live Chrome browser for debugging, automation, and performance work. It exposes Chrome DevTools capabilities through MCP, so agents can inspect network traffic, collect traces, capture screenshots, and automate browser actions from the same server."
github_stars: 34239
verification: "security_reviewed"
source: "https://github.com/ChromeDevTools/chrome-devtools-mcp"
author: "ChromeDevTools"
publisher_type: "Open Source Project"
category: "Browser Automation"
framework: "MCP"
tool_ecosystem:
github_repo: "ChromeDevTools/chrome-devtools-mcp"
github_stars: 34239
npm_package: "chrome-devtools-mcp"
npm_weekly_downloads: 1759009
---
# Chrome DevTools MCP Browser Debugging and Performance Analysis
Chrome DevTools MCP connects an MCP-compatible agent to a live Chrome browser for debugging, automation, and performance work. It exposes Chrome DevTools capabilities through MCP, so agents can inspect network traffic, collect traces, capture screenshots, and automate browser actions from the same server.
## Prerequisites
Node.js v20.19+, Google Chrome, npm
## Installation
Requirements and caveats from upstream:
- [Node.js](https://nodejs.org/) [LTS](https://github.com/nodejs/Release#release-schedule) version.
Basic usage or getting-started notes:
- this, run with the --no-performance-crux flag.
- ## **Usage statistics**
- Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.
- Source: https://github.com/ChromeDevTools/chrome-devtools-mcp
- Extracted from upstream docs: https://raw.githubusercontent.com/ChromeDevTools/chrome-devtools-mcp/HEAD/README.md
## Documentation
- https://github.com/ChromeDevTools/chrome-devtools-mcp
## Source
- [Agent Skill Exchange](https://agentskillexchange.com/skills/chrome-devtools-mcp-browser-debugging-performance-analysis/)
