chrome-devtools-mcp
Verified Safeby ChromeDevTools
Overview
Enables AI coding agents to control and inspect a live Chrome browser for reliable automation, in-depth debugging, and performance analysis via the Model-Context-Protocol (MCP).
Installation
npx -y chrome-devtools-mcp@latestEnvironment Variables
- DEBUG
Security Notes
The `evaluate_script` tool explicitly allows AI agents to execute arbitrary JavaScript within the browser context, enabling inspection, debugging, and modification of any data in the browser or DevTools. This is a core, intended feature for powerful automation but inherently carries a significant security risk if the AI client or its prompts are compromised. The server launches or connects to a full Chrome instance, and users are explicitly warned against sharing sensitive information with MCP clients. If connecting to a manually launched browser, enabling the remote debugging port (`--remote-debugging-port`) opens up a debugging interface that any application on the machine can connect to.
Similar Servers
inspector
Inspect, debug, and interact with Model Context Protocol (MCP) servers, including OAuth authentication flows, resource management, and tool execution.
mcp-server-browserbase
Provides cloud browser automation capabilities, enabling LLMs to interact with web pages, take screenshots, extract information, and perform automated actions.
brightdata-mcp
The MCP server enables AI agents to access real-time web data and perform browser automation for tasks like research, e-commerce intelligence, market analysis, and content creation, bypassing bot detection and CAPTCHAs.
flowlens-mcp-server
Provides rich browser context (user actions, network, console, storage, DOM, screen recording) to coding agents for in-depth debugging and automated regression testing of web applications.