Chrome Devtools MCP

What chrome-devtools-mcp does

chrome-devtools-mcp gives MCP-compatible coding agents control over and inspection access to Google Chrome and Chrome for Testing. Agents can open, select, navigate, resize, and close pages; interact with page elements; inspect browser output; and collect diagnostic data through Chrome DevTools.

The server supports both routine browser automation and deeper debugging. Interaction tools cover clicking, dragging, hovering, filling fields and forms, typing, key presses, file uploads, dialog handling, and waiting for page conditions. Inspection tools expose console messages, network requests, screenshots, page snapshots, and evaluated JavaScript. Performance features record traces, analyze performance insights, and run Lighthouse audits.

Use it for agent-assisted web debugging, end-to-end browser tasks, performance investigations, and checking how a page behaves in a real Chrome session.

How it works

The package runs as an MCP server and can be launched by an MCP client with npx. It also includes a separate chrome-devtools command-line interface for terminal-based browser control. The MCP server does not launch Chrome merely because a client connects; Chrome starts when the client first invokes a tool that needs an active browser instance.

Browser actions use Puppeteer and wait automatically for action results. DevTools-oriented capabilities use the connected Chrome instance to gather traces, inspect requests and console output, capture screenshots, and analyze page performance. Performance analysis may query the Google CrUX API using trace URLs to add real-user experience data to lab results.

Setup and configuration

Install Node.js LTS, a current stable Chrome release or newer, and npm. Add the following MCP server entry to the client configuration:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": ["-y", "chrome-devtools-mcp@latest"]
    }
  }
}

The package supports server parameters such as --headless, --isolated, and --slim, along with configuration for WebSocket connections. Advanced configurations cover concurrent sessions, persistent user-data directories, connecting to an existing Chrome instance, and Android debugging.

Usage statistics are enabled by default. Start the server with --no-usage-statistics to opt out. Statistics collection is also disabled when CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI is set. Update notifications can be disabled with CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS. Use --no-performance-crux to prevent performance tools from requesting CrUX data.

Tools and capabilities

• Automate pages with click, drag, fill, fill_form, hover, type_text, press_key, upload_file, and handle_dialog.
• Manage browser pages with new_page, list_pages, select_page, navigate_page, wait_for, resize_page, and close_page.
• Inspect and capture page state with evaluate_script, take_snapshot, take_screenshot, and screencast_start.
• Diagnose runtime behavior with list_console_messages, get_console_message, list_network_requests, and get_network_request.
• Measure performance with performance_start_trace, performance_stop_trace, performance_analyze_insight, and lighthouse_audit.
• Model browser conditions with emulate and perform coordinate-based interactions with click_at.

Limitations and notes

The supported browsers are Google Chrome and Chrome for Testing. Other Chromium-based browsers may work, but are not guaranteed. The server exposes browser contents to MCP clients, allowing them to inspect, debug, and modify data in the browser or DevTools; avoid using it with sensitive information that should not be shared.

Google collects tool usage statistics by default, including invocation success rates, latency, and environment information. This collection is separate from Chrome browser metrics. Performance tools can also send trace URLs to Google CrUX unless that behavior is disabled with --no-performance-crux.

Skills included with the package describe MCP and CLI workflows, accessibility debugging, cookie and authentication debugging, Largest Contentful Paint optimization, memory-leak debugging, and connection troubleshooting. Skills should be updated when the server or CLI package is updated because they can refer to version-specific tools or parameters.