MCP or Not?
OfficialClaude connector: not verified

Chrome DevTools MCP server & Claude connector

Does Chrome DevTools have an official MCP server or Claude connector?

Official

As of October 2026, Chrome DevTools has an official MCP server (chrome-devtools-mcp) published by Google's ChromeDevTools organization and announced on developer.chrome.com. It runs locally via npx, needs no account, and controls a live Chrome for debugging, performance traces and automation. Caveats: it exposes browser content to the client, and usage statistics are on by default.

Last checked

Verdict and evidence

What we checked
Chrome DevTools MCP
Published by
Google (ChromeDevTools) (official)
Runs
Runs locally
Sign-in
None
Stage
Generally available
Plan
Free and open source; requires Node.js LTS and current stable Chrome.

Evidence

What an AI can do in Chrome DevTools

Read

  • Run a Lighthouse auditlighthouse_audit
  • List network requestslist_network_requests
  • List console messageslist_console_messages
  • Take a page snapshot from the accessibility treetake_snapshot

Update

  • Fill a form fieldfill

Run

  • Start a performance traceperformance_start_trace
  • Click an elementclick
  • Evaluate JavaScript in the pageevaluate_script

From the publisher’s documentation for the version we checked. Not every tool is listed.

Setup

Claude (claude.ai / Desktop)

Standard config for any MCP client, including Claude Desktop.

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

Claude Code

Add via the Claude Code CLI (a plugin with skills is also documented).

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

Cursor

Cursor is covered in the client configurations guide; use the standard config.

Source

VS Code

Install via CLI or the VS Code install button.

code --add-mcp '{"name":"io.github.ChromeDevTools/chrome-devtools-mcp","command":"npx","args":["-y","chrome-devtools-mcp"],"env":{}}'
Source

Safety check

  • Pass

    Publisher verified

    Repo is in the ChromeDevTools GitHub organization, whose homepage is devtools.chrome.com; the repo homepage is developer.chrome.com/docs/devtools/agents and Google's Chrome for Developers blog announces it.

  • Pass

    Auth model

    No account or key; launches or connects to a local Chrome. The README warns it exposes browser content to MCP clients, allowing them to inspect, debug and modify any data in the browser.

  • Flag

    Write and delete access

    Exposes click, fill, upload_file, evaluate_script, install_extension and similar tools with no documented read-only mode. Tools are grouped by category and can be turned off with --category-* flags in the configuration guide.

  • Pass

    Tool-description injection scan

    Read the generated tool reference (input, navigation, emulation, performance, network, debugging, memory, extensions groups). Only usage guidance such as 'Always use the latest snapshot' was found; nothing that hides actions or exfiltrates data. Page content is still untrusted.

  • Pass

    Repo maintenance

    ChromeDevTools/chrome-devtools-mcp: not archived, last push 2026-10-18, about 53,800 stars.

FAQ

Is the Chrome DevTools MCP server official?

Yes. It is published by Google's ChromeDevTools organization and announced on the Chrome for Developers blog.

Is it free?

Yes. It is open source and runs locally with npx; it needs Node.js and Chrome.

Does it work with Claude Code and Cursor?

Yes. The client configurations guide documents Claude Code (claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest), Cursor, VS Code and others.

What data does it send to Google?

Per the README, usage statistics are collected by default (opt out with --no-usage-statistics), and performance tools may send trace URLs to the Chrome UX Report API (opt out with --no-performance-crux).

Is there a read-only mode?

No dedicated read-only mode was found as of October 2026. A --slim mode exposes a basic tool set, and tool categories can be disabled with --category flags.

Last reviewed .

Get your badge

Work at Chrome DevTools? Show that your MCP server is independently checked. The badge reflects this page: it updates when we re-check, and it links readers to the evidence.

MCP or Not: Official · Checked Oct 2026

Markdown (README)

[![MCP or Not: Official · Checked Oct 2026](https://mcpornot.com/badge/chrome-devtools.svg)](https://mcpornot.com/chrome-devtools)

HTML

<a href="https://mcpornot.com/chrome-devtools"><img src="https://mcpornot.com/badge/chrome-devtools.svg" alt="MCP or Not: Official · Checked Oct 2026" height="20"></a>

Compare Chrome DevTools

Something changed?

Vendors ship MCP updates often. If Chrome DevTools launched, changed or retired a server, tell us and we will re-check it against primary sources. Submit a correction.

New official MCP servers, weekly

One short email when vendors ship, change or retire an official server or Claude connector. Checked against primary sources, like every verdict here.