Chrome DevTools MCP Server: Tools, Setup and Security

Chrome DevTools MCP lets an AI coding agent control and inspect a live Chrome browser. It can record performance traces, read network requests and console messages, take screenshots and run Lighthouse audits. The Chrome DevTools team publishes it as open source, and Google handles its usage data. As of October 2026, the README calls the project "Chrome DevTools for agents" and offers it as an MCP server and a CLI; the package is still chrome-devtools-mcp.

Checked against: Chrome DevTools MCP on GitHub on 28 October 2026. eSEOspace did not install or test this server.

At a glance

What it can do

The project's tool reference lists 60 tools in 12 groups as of October 2026. The main groups:

• Input automation: click, click_at, fill, fill_form, type_text, press_key, hover, drag, upload_file, handle_dialog
• Navigation: new_page, navigate_page, list_pages, select_page, close_page, wait_for
• Emulation: emulate, resize_page
• Performance: performance_start_trace, performance_stop_trace, performance_analyze_insight
• Network: list_network_requests, get_network_request
• Debugging: evaluate_script, list_console_messages, get_css_styles, lighthouse_audit, take_screenshot, take_snapshot
• Memory: take_heapsnapshot and a set of heap snapshot analysis tools
• Extensions: install_extension, list_extensions, reload_extension, trigger_extension_action, uninstall_extension
• Newer groups: Third-party developer tools, WebMCP (list_webmcp_tools, execute_webmcp_tool), Progressive Web Apps (install_pwa, launch_pwa and two more) and WebAuthn (configure_webauthn)

A --slim flag exposes a reduced set of tools for basic browser tasks. The package also ships a chrome-devtools CLI and skills for accessibility, cookies, LCP (Largest Contentful Paint) and memory leaks.

How to connect it

Add this to your MCP client config:

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

For Claude Code, the client guide gives:

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

You need a current Node.js LTS release, current stable Chrome and npm. The README suggests a first test prompt: "Check the performance of https://developers.chrome.com".

Security notes

The README is direct about risk. The server "exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools."

Practical steps:

• Opt out of data sharing with --no-usage-statistics and --no-performance-crux if your policy requires it. Usage collection is also off when the CI or CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS environment variable is set.
• Use an isolated profile. The configuration guide lists --isolated and --headless options.
• Avoid logged-in sessions with customer data, payment details or admin access.
• Watch powerful tools. evaluate_script runs JavaScript in the page, and the extension tools can install or remove browser extensions.

Only Google Chrome and Chrome for Testing are officially supported. Other Chromium browsers may work but are not guaranteed.

The MCP project's security best practices also cover risks such as token passthrough, confused deputy attacks and scope minimization.

Read data exfiltration through MCP and sandboxing local MCP servers, and visit the MCP Security Center.

Alternatives

• Playwright MCP server for cross-browser automation from Microsoft.
• Sentry MCP server for errors and traces from real users in production.
• JetBrains MCP server if you want the AI working inside your IDE instead.

Next step

Use Chrome DevTools MCP on a staging site to chase Core Web Vitals issues, with usage statistics set to match your policy. Our best MCP servers for developers list shows how it fits with other tools, and the MCP server directory has more.

Frequently asked questions