browser-automationdebuggingperformancedevtools

Summary

Google's official MCP server for controlling and inspecting a live Chrome browser from coding agents.

Features

  • Drive and inspect a live Chrome browser
  • Read console messages and network requests
  • Record and analyze performance traces / Core Web Vitals
  • Available as a standalone MCP server or a Claude Code plugin

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it.
  3. Restart the agent — the "Chrome DevTools MCP" tools will be available.
{
  "mcpServers": {
    "chrome-devtools-mcp": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

Description

Chrome DevTools MCP, maintained by the Google Chrome DevTools team, gives coding agents direct access to a real Chrome browser through the Chrome DevTools Protocol. It supports reliable browser automation (navigation, clicking, form filling), in-depth debugging (console messages, network requests, DOM inspection), and performance analysis (recording and analyzing traces, Core Web Vitals) — all driven from natural-language instructions instead of hand-written Puppeteer scripts. It officially supports Google Chrome and Chrome for Testing, and ships both as a standalone MCP server and as a Claude Code plugin bundling matching skills.

Related MCP Servers

Browse all MCP servers →