OfficialDeveloper Tools

Chrome DevTools

by Google

Let a coding agent drive a live Chrome browser to debug pages, inspect network traffic and record performance traces.

Best for

Coding agents that should check their own front-end changes in a real Chrome: reading console errors, watching network calls and measuring performance after an edit.

Connect Chrome DevTools

Choose your client

Local

This server runs on your machine. Pick your client for the matching config; placeholders stand in for any secrets.

Before you connect

The server exposes the content of the browser instance to the MCP client, which can inspect, debug and modify any data in the browser or DevTools. The README advises against sharing sensitive or personal information you don't want the client to see.

claude_desktop_config.json
{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp"
      ]
    }
  }
}
  • Add this under the existing mcpServers key if the file already has one, then fully restart Claude Desktop.

Format checked Oct 30, 2026 against Claude Desktop documentation. Client settings change, so confirm with the client's own docs.

Connection details

Package

npm package · stdio
chrome-devtools-mcp@1.12.0

Overview

Chrome DevTools MCP gives a coding assistant the inspection tools a developer would reach for in the browser. It can open a page, read console messages with source-mapped stack traces, look at network requests, take screenshots and record performance traces, then act on the page through Puppeteer-based automation. It runs on your machine through npx and starts Chrome only when a tool needs a browser. The README says performance tools may send trace URLs to the Google CrUX API for field data, and that usage statistics are collected unless you opt out with a flag.

What it can do

  • Records performance traces and pulls actionable insights out of them using Chrome DevTools.
  • Reads console messages with source-mapped stack traces, inspects network requests and takes screenshots.
  • Automates actions in Chrome through Puppeteer and waits for each action's result before moving on.
  • The same package includes a chrome-devtools command-line interface for using the browser tools without MCP.

What you need

Sign-in and credentials

No account or API key is mentioned. It needs a current Node.js LTS release, npm and the current stable Chrome. The README says only Google Chrome and Chrome for Testing are officially supported.

Runs as

npm package

Sources

MCP Registry
Listed in the MCP Registry as io.github.ChromeDevTools/chrome-devtools-mcp
Last checked
Oct 31, 2026
Record reviewed
Oct 31, 2026

Statements on this page come from

Why is this labelled Official?

Registry name io.github.ChromeDevTools/chrome-devtools-mcp. The registry only lets an organization's owners publish under its io.github.<org> namespace (registry authentication docs, read 2026-10-30). The repository is in the ChromeDevTools organization, which also holds the DevTools frontend the README links to, and the README says Google collects usage statistics for Chrome DevTools MCP under the Google Privacy Policy (read 2026-10-31).

Listing on HistChat is not an endorsement or a security review. MCP servers can access data or perform actions, so review the source and permissions before connecting.

  • Sentry

    SentryOfficial

    Search errors and traces, triage issues and debug failures in Sentry from a coding assistant.

    Category
    Developer Tools
    Connection
    Remote · Local
  • GitHub

    GitHubOfficial

    Let an assistant browse repositories, triage issues, handle pull requests and check Actions runs on GitHub.

    Category
    Developer Tools
    Connection
    Remote · Local
    GitHub stars
    34k
  • Grafana

    Grafana LabsOfficial

    Search dashboards, query Prometheus and Loki, and work with incidents in a Grafana instance from an assistant.

    Category
    Developer Tools
    Connection
    Local
    GitHub stars
    3.6k
  • GitLab

    GitLabOfficial

    Connect an assistant to GitLab projects, issues and merge requests through the MCP endpoint built into GitLab itself.

    Category
    Developer Tools
    Connection
    Remote
  • Filesystem

    Model Context ProtocolReference

    Let an assistant read, search and edit files in the folders you choose on your own machine.

    Category
    Developer Tools
    Connection
    Local
  • Playwright

    MicrosoftOfficial

    Give an assistant control of a real browser to navigate pages, click, type and read page structure.

    Category
    Browser & Web
    Connection
    Local
    GitHub stars
    39k