MCP Catalogs
Home

chrome-devtools-mcp

by ChromeDevTools·39,757·Score 65

Chrome DevTools MCP server lets AI coding agents control and inspect live Chrome browsers through the MCP protocol.

browser-automationdeveloper-toolsweb-scraping
2,527
Forks
97
Open issues
this month
Last commit
2d ago
Indexed

Overview

Chrome DevTools for Agents provides AI coding assistants with access to Chrome's full capabilities including performance analysis, network debugging, and browser automation. It uses Puppeteer for reliable automation and Chrome DevTools for deep inspection. The server exposes tools for recording traces, taking screenshots, analyzing network requests, and accessing console messages with source-mapped stack traces.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:Automated web testing and validation by AI agents
you:Performance analysis and optimization of web applications
you:Debugging web applications through AI-powered inspection
you:Which browsers are supported?
you:Is usage data collected?

When to choose this

When you need your AI coding agent to have full control and debugging capabilities for Chrome browser instances during development and testing workflows.

When NOT to choose this

If you need browser automation for browsers other than Chrome, or if you're concerned about Google collecting usage statistics despite the ability to opt-out.

Tools this server exposes

12 tools extracted from the README
  • navigatenavigate(url: string)

    Navigate the browser to a specific URL

  • clickclick(selector: string)

    Click on an element matching the given selector

  • typetype(selector: string, text: string)

    Type text into an element matching the given selector

  • screenshotscreenshot()

    Take a screenshot of the current page

  • get_elementget_element(selector: string)

    Get information about an element matching the given selector

  • get_elementsget_elements(selector: string)

    Get information about all elements matching the given selector

  • get_page_titleget_page_title()

    Get the title of the current page

  • get_page_sourceget_page_source()

    Get the HTML source of the current page

  • get_console_messagesget_console_messages()

    Get console messages from the browser

  • get_network_requestsget_network_requests()

    Get network requests made by the browser

  • evaluateevaluate(script: string)

    Execute JavaScript in the current page

  • wait_for_selectorwait_for_selector(selector: string)

    Wait for an element to appear on the page

Note: Tool names and descriptions extracted from the tool reference documentation mentioned in the README.

Comparable tools

playwright-mcpbrowserless-mcppuppeteer

Installation

Installation

Add the following config to your MCP client:

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

For basic browser tasks in headless mode:

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

FAQ

Which browsers are supported?
Chrome DevTools MCP officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work but aren't guaranteed.
Is usage data collected?
Yes, Google collects usage statistics by default to improve reliability and performance. You can opt-out with the --no-usage-statistics flag.

On Hacker News

Recent discussion from the developer community.

Compare chrome-devtools-mcp with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.