← Back to all projects

chrome-devtools-mcp

The Chrome team's MCP server: an agent that reads performance traces, network and console, not just the page

MCP serverOfficialApache-2.0
Stars
54.5k
Forks
5.9k
Open issues
121
Last commit
30 Oct 2026

What is chrome-devtools-mcp?

It hands an agent a live Chrome plus the instruments of DevTools: it records a performance trace and reads out Core Web Vitals with named insights, lists network requests and source-mapped console errors, runs Lighthouse audits, and still clicks and fills forms from a text snapshot of the page the way browser MCPs do. It can attach to the Chrome you already have open, profile and all — which is also where care is needed. The trade against Playwright MCP is scope: this is Chrome-only, and what that buys is analysis no cross-browser server offers.

What can you do with chrome-devtools-mcp?

  • A performance engineer's view, summarised for the model — Trace recording ends in named insights and Core Web Vitals — the agent reads "LCP was 3.2s" rather than a raw trace file. By default it also pulls real-user field data from Google's CrUX service for the traced URL, and a Lighthouse audit is one tool call.
  • Debugging from what the browser actually said — Console messages arrive source-mapped, network requests can be listed and opened individually, arbitrary JavaScript runs in the page, and screenshots or screencasts capture what a human would have seen.
  • Attach to the Chrome you already use — It launches its own Chrome with a persistent profile by default, swaps to a throwaway one with --isolated, or attaches to a running browser — including your own profile and logins on recent Chrome. Channel selection reaches beta, dev and canary builds.
  • Fifty-seven tools, but you choose the surface — Memory analysis, extension and PWA toolsets stay off until asked for; device emulation and throttling are on; and a slim mode collapses everything to three tools — navigate, evaluate, screenshot — when a small tool list matters more than instrumentation.

Before you choose chrome-devtools-mcp

  • Its own README warns that the connected browser's content is exposed to the MCP client and can be inspected or modified — attaching the Chrome you actually browse with hands the model whatever is open in it.
  • Google's usage statistics are collected by default and performance traces query the CrUX service unless disabled — both are opt-out flags, not opt-in choices.

Star history

19 Aug to 30 Oct · +5.1k

49.4k54.5k

Frequently asked questions

Is chrome-devtools-mcp free for commercial use?

chrome-devtools-mcp is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.

How can chrome-devtools-mcp be deployed?

chrome-devtools-mcp is available as Runs locally.

chrome-devtools-mcp
Ask AI
GitHub