Chrome DevTools MCP

io.github.ChromeDevToolsPublished by GitHub account ChromeDevToolsv1.12.0Updated Oct 29, 2026

MCP server for Chrome DevTools

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets a coding agent control and inspect a live Chrome browser for automation, debugging and performance analysis.

What you can do
  • Navigate, open, select, resize and close pages, and wait for text to appear
  • Click, hover, drag, type, press keys, fill forms, upload files and handle dialogs
  • Take accessibility-tree snapshots, screenshots and screencasts, and read matched CSS styles
  • Inspect console messages and network requests, and run JavaScript in the page
  • Record performance traces, analyze insights, run Lighthouse audits and capture heap snapshots
When to use it
Useful when an agent needs to drive a real Chrome session: reproducing and debugging frontend bugs, checking console and network behavior, auditing accessibility or SEO, or measuring load performance and Core Web Vitals.
Requirements
Runs locally over stdio via npx from the npm package chrome-devtools-mcp. Needs Node.js LTS, npm and a current stable Chrome (or Chrome for Testing); the browser starts automatically on the first tool call that needs it. No accounts, API keys or headers are declared.
Before you install
The server exposes the browser's content to the MCP client, which can inspect, debug and modify any data in the browser, so avoid sensitive or personal information. It can click, type, upload files and run JavaScript on pages. Usage statistics are collected by default and can be disabled with the --no-usage-statistics flag or the CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS variable; performance tools may send trace URLs to the Google CrUX API unless --no-performance-crux is set.

Installation

In SourceWeft

  1. Open Chrome DevTools MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Chrome DevTools for agents

[npm chrome-devtools-mcp package]

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent (such as Antigravity, Claude, Cursor or Copilot) control and inspect a live Chrome browser. It is available as a Model-Context-Protocol (MCP) server and as a CLI. Both give your AI coding assistant access to the full power of Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.

Tool reference | CLI | Skills | Changelog | Contributing | Troubleshooting | Design Principles

Key features

  • Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights.
  • Advanced browser debugging: Analyze network requests, take screenshots and check browser console messages (with source-mapped stack traces).
  • Reliable automation. Uses puppeteer to automate actions in Chrome and automatically wait for action results.

Disclaimers

chrome-devtools-mcp exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information that you don't want to share with MCP clients.

chrome-devtools-mcp officially supports Google Chrome and Chrome for Testing only. Other Chromium-based browsers may work, but this is not guaranteed, and you may encounter unexpected behavior. Use at your own discretion. We are committed to providing fixes and support for the latest version of Extended Stable Chrome.

Performance tools may send trace URLs to the Google CrUX API to fetch real-user experience data. This helps provide a holistic performance picture by presenting field data alongside lab data. This data is collected by the Chrome User Experience Report (CrUX). To disable this, run with the --no-performance-crux flag.

Usage statistics

Google collects usage statistics (such as tool invocation success rates, latency, and environment information) to improve the reliability and performance of Chrome DevTools MCP.

Data collection is enabled by default. You can opt-out by passing the --no-usage-statistics flag when starting the server:

json
"args": ["-y", "chrome-devtools-mcp@latest", "--no-usage-statistics"]

Google handles this data in accordance with the Google Privacy Policy.

Google's collection of usage statistics for Chrome DevTools MCP is independent from the Chrome browser's usage statistics. Opting out of Chrome metrics does not automatically opt you out of this tool, and vice-versa.

Collection is disabled if CHROME_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI env variables are set.

Update checks

By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available. You can disable these update checks by setting the CHROME_DEVTOOLS_MCP_NO_UPDATE_CHECKS environment variable.

Requirements

Getting started

Add the following config to your MCP client:

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

[!NOTE] Using chrome-devtools-mcp@latest ensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.

MCP Client configuration

For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide.

Your first prompt

Enter the following prompt in your MCP Client to check if everything is working:

Check the performance of https://developers.chrome.com

Your MCP client should open the browser and record a performance trace.

[!NOTE] The MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Chrome DevTools MCP server on its own will not automatically start the browser.

CLI

The package also includes the chrome-devtools CLI. Use it to control the browser from your terminal without MCP:

sh
npm i chrome-devtools-mcp@latest -gchrome-devtools navigate_page 1 --url "https://developers.chrome.com"chrome-devtools take_screenshot 1 --filePath screenshot.pngchrome-devtools stop

See the CLI guide for all commands and options.

Skills

The package includes skills that teach your agent how to use Chrome DevTools:

SkillUse it to
chrome-devtoolsDebug and automate pages with the MCP tools.
chrome-devtools-cliRun the CLI and write shell scripts with it.
a11y-debuggingAudit and fix accessibility issues.
cookie-debuggingDebug cookies, sessions, and authentication.
debug-optimize-lcpDebug and improve Largest Contentful Paint.
memory-leak-debuggingFind and fix memory leaks.
troubleshootingFix connection problems between MCP and Chrome.

Install skills as a plugin

A plugin installs the MCP server and all skills, including the CLI skill:

  • Claude Code: Run /plugin marketplace add ChromeDevTools/chrome-devtools-mcp, then /plugin install chrome-devtools-mcp@chrome-devtools-plugins.
  • Copilot / VS Code: Run Chat: Install Plugin From Source and enter ChromeDevTools/chrome-devtools-mcp.
  • Gemini CLI: Run gemini extensions install --auto-update https://github.com/ChromeDevTools/chrome-devtools-mcp.

See the Client Configurations Guide for more information.

Install skills manually

If your agent does not support plugins, copy the skill folders into the skills directory of your agent. The npm package contains the skills:

sh
npm i chrome-devtools-mcp@latest -g# Example for Claude Code. Use the skills directory of your agent.mkdir -p ~/.claude/skillscp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/

[!IMPORTANT] The chrome-devtools-cli skill requires the CLI. Install the package globally before you use the skill.

Keep skills up to date

Skills describe the tools of a specific version. Update the skills each time you update the MCP server or the CLI. Outdated skills can tell your agent to use tools or parameters that changed.

  • Plugins: Use the update command of the plugin manager of your agent. The Gemini CLI command above enables automatic updates with --auto-update.
  • Manual installs: Update the package, then copy the skill folders again:
sh
npm i chrome-devtools-mcp@latest -gmkdir -p ~/.claude/skillscp -R "$(npm root -g)/chrome-devtools-mcp/skills/chrome-devtools-cli" ~/.claude/skills/

Tools

If you run into any issues, checkout our troubleshooting guide. See the full Tool Reference for a complete list of all supported MCP capabilities.

Configuration

Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.

For basic browser tasks only, the --slim flag exposes a reduced set of tools. See the Slim tool reference.

Advanced Usage

For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Chrome instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.

Integrating as a browser subagent

If you are developing agentic tooling and want to provide an integrated browser subagent as part of your product, we recommend building on top of Chrome DevTools for agents.

For a reference implementation, see the Gemini CLI browser agent documentation.

Source: README.md at commit af28344

Tools

32

click

Clicks on the provided element

ParametersuidrequiredpageIdrequireddblClickincludeSnapshot

close_page

Closes the page by its index. The last open page cannot be closed.

ParameterspageIdrequired

drag

Drag an element onto another element

ParameterspageIdrequiredto_uidrequiredfrom_uidrequiredincludeSnapshot

emulate

Emulates various features on the target page. Each call replaces all emulation settings (except extraHttpHeaders), so pass all desired settings in a single call.

ParameterspageIdrequiredviewportuserAgentcolorSchemegeolocationforcedColorsprefersContrastextraHttpHeaderscpuThrottlingRatenetworkConditionsprefersReducedMotion

evaluate_script

Evaluate JavaScript inside the target page. The source can be provided inline or loaded from a local file. Returns the response as JSON, so returned values have to be JSON-serializable.

ParametersargsformatpageIdrequiredfilePathfunctionsourcePathdialogActionwaitForStableDom

fill

Type text into an input, text area or select an option from a <select> element.

ParametersuidrequiredvaluerequiredpageIdrequiredincludeSnapshot

fill_form

Fill out multiple form elements (inputs, selects, checkboxes, radios) at once. ALWAYS prefer this tool over multiple individual 'fill' or 'click' calls when interacting with forms. It is significantly faster, more reliable, and reduces turn count. Example: Fill username, password, and check "Remember Me" in one call.

ParameterspageIdrequiredelementsrequiredincludeSnapshot

get_console_message

Gets a console message by its ID. You can get all messages by calling list_console_messages.

ParametersmsgidrequiredpageIdrequired

get_css_styles

Retrieve matched CSS rules, inline styles (element.style), inherited styles, custom properties, and cascade wrappers (@layer, @media, @container, @scope) for an element identified by its UID. Rules are ordered from highest to lowest cascade precedence and include source line numbers (e.g. index:196). Active (winning) declarations have no prefix tag, while (losing) overridden declarations are prefixed with [overloaded]. Treat the output as authoritative and complete. Results are paginated (10 rules per page by default); use pageIdx to page through the remaining rules. Requires a UID from take_snapshot.

ParametersuidrequiredpageIdrequiredpageIdxpageSize

get_network_request

Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel. Useful for inspecting request headers (including 'Cookie') and response headers (including 'Set-Cookie' and directives).

ParametersreqidpageIdrequiredrequestFilePathresponseFilePath

handle_dialog

If a browser dialog was opened, use this command to handle it

ParametersactionrequiredpageIdrequiredpromptText

hover

Hover over the provided element

ParametersuidrequiredpageIdrequiredincludeSnapshot

lighthouse_audit

Get Lighthouse scores, failing audits, and the DOM nodes they flag for accessibility, SEO, best practices, and agentic browsing. Full reports are saved to disk. This excludes performance. For performance audits, run performance_start_trace

ParametersmodedevicepageIdrequiredoutputDirPath

list_console_messages

List all console messages for the target page since the last navigation.

ParameterstypespageIdrequiredpageIdxpageSizeserviceWorkerIdincludeStackTracesincludePreservedMessages

list_network_requests

Lists the most recent requests for the target page since the last navigation.

ParameterspageIdrequiredpageIdxpageSizeresourceTypesincludePreservedRequests

list_pages

Get a list of pages open in the browser.

Takes no parameters.

navigate_page

Go to a URL, or back, forward, or reload. Use project URL if not specified otherwise.

ParametersurltypepageIdrequiredtimeoutinitScriptignoreCachehandleBeforeUnload

new_page

Open a new tab and load a URL. Use project URL if not specified otherwise.

ParametersurlrequiredtimeoutbackgroundisolatedContext

performance_analyze_insight

Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording.

ParameterspageIdrequiredinsightNamerequiredinsightSetIdrequired

performance_start_trace

Start a performance trace on the target webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed.

ParameterspageIdrequiredreloadautoStopfilePathignoreCache

performance_stop_trace

Stop the active performance trace recording on the target webpage.

ParameterspageIdrequiredfilePath

press_key

Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations).

ParameterskeyrequiredpageIdrequiredincludeSnapshot

resize_page

Resizes the page's window so that the page has specified dimension

ParameterswidthrequiredheightrequiredpageIdrequired

screencast_start

Starts recording a screencast (video) of the target page.

ParameterspageIdrequiredfilePath

screencast_stop

Stops the active screencast recording on the target page.

ParameterspageIdrequired

select_page

Select a page as a context for future tool calls.

ParameterspageIdrequiredbringToFront

take_heapsnapshot

Capture a heap snapshot of the target page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks.

ParameterspageIdrequiredfilePathrequired

take_screenshot

Take a screenshot of the page or element.

ParametersuidformatpageIdrequiredqualityfilePathfullPage

take_snapshot

Take a text snapshot of the target page based on the a11y tree. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected in the DevTools Elements panel (if any).

ParameterspageIdrequiredverbosefilePath

type_text

Type text using keyboard into a previously focused input

ParameterstextrequiredpageIdrequiredsubmitKey

upload_file

Upload a file through a provided element.

ParametersuidrequiredpageIdrequiredfilePathsrequiredincludeSnapshot

wait_for

Wait for the specified text to appear on the selected page. By default, hidden text is also matched. Set visible to true to wait until the matched text is visible.

ParameterstextrequiredpageIdrequiredtimeoutvisible

Version history

4
  1. v1.12.0LatestOct 22, 2026
  2. v1.11.0Oct 15, 2026
  3. v1.10.1Sep 23, 2026
  4. v1.9.0Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts