Skip to content
Chrome Devtools logo

Chrome Devtools

Verified

Control and inspect live Chrome via DevTools for AI coding agents.

MCP ServerSearch & WebLocal (stdio) 43.6k
View on GitHub
Updated 2026-06-15

What is the Chrome Devtools MCP server?

Chrome DevTools MCP lets agents record traces, extract performance insights, debug network activity, and examine console messages with source maps. It automatically waits for actions and works with Google Chrome or Chrome for Testing.

The package is installed via npm and configured in MCP clients using npx. Optional flags disable usage statistics, CrUX data, or update checks while slim mode reduces the tool surface for basic tasks.

Install & connect

Add this to your MCP client config. Pick your client below and copy.

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

Package: chrome-devtools-mcp (npm)

Other ways to install

npx

npx
npx -y chrome-devtools-mcp

Example prompts

Once connected, try asking your AI client:

Take a screenshot of the current page and describe the layout
Analyze network requests for the last page load and list any failed ones
Record a performance trace and summarize the main bottlenecks
Check the console for errors and show source-mapped stack traces

Security & permissions

Runs locally via stdio and exposes the full browser session to the MCP client; avoid using with sensitive tabs or data.

What you can do with Chrome Devtools

Performance analysis

Record traces and combine lab data with real-user CrUX metrics to identify bottlenecks.

Debugging web apps

Inspect network requests, view console errors with source maps, and capture screenshots.

Browser automation

Automate interactions in Chrome and wait for results without writing custom scripts.

How to use Chrome Devtools

  1. 1Install Node.js LTS and a recent stable Chrome browser.
  2. 2Add the server config to your MCP client using npx chrome-devtools-mcp@latest.
  3. 3Optionally append --slim --headless or --no-usage-statistics.
  4. 4Restart the MCP client so it starts the stdio server.
  5. 5Ask your coding agent to perform browser actions or inspections.

Chrome Devtools: pros & cons

Pros

  • +Direct access to Chrome DevTools features inside AI workflows
  • +Reliable automation with automatic waiting via Puppeteer
  • +Performance insights combining lab traces and field CrUX data
  • +Simple npm-based installation and updates

Cons

  • Requires a local Chrome instance and Node.js
  • Exposes all browser content to the MCP client
  • Usage statistics collected by default unless opted out
Did you find this helpful?

Frequently asked questions

Only Google Chrome and Chrome for Testing are officially supported.

User reviews

Verified reviews from the community shape this listing's rating.

Loading reviews…

Sign in to review

Promote Chrome Devtools

Add this badge to your website, or share the tool.

DFeatured on DhanasviChrome Devtools 2