
The Chrome DevTools MCP server enables AI coding agents to control and inspect live Chrome browser instances through the Model Context Protocol, providing tools for performance analysis, advanced debugging, and reliable automation. It offers capabilities including performance trace recording and analysis, network request inspection, screenshot capture, console message analysis with source mapping, and browser action automation via Puppeteer. The server solves the problem of giving AI assistants direct access to Chrome DevTools functionality for in-depth debugging, performance optimization, and reliable browser automation tasks.
claude mcp add chrome-devtools-mcp -- npx -y chrome-devtools-mcpRun in your terminal. Replace YOUR_* placeholders with real values; add --scope user to install for every project.
Review the command, arguments, and environment values before installing — MCP servers run with your local permissions.
Verified live against the running server on Jun 10, 2026.
clickClicks on the provided element3 paramsClicks on the provided element
dblClickbooleanincludeSnapshotbooleanuid*stringclose_pageCloses the page by its index. The last open page cannot be closed.1 paramsCloses the page by its index. The last open page cannot be closed.
pageId*numberdragDrag an element onto another element3 paramsDrag an element onto another element
from_uid*stringincludeSnapshotbooleanto_uid*stringemulateEmulates various features on the selected page.7 paramsEmulates various features on the selected page.
colorSchemestringdark · light · autocpuThrottlingRatenumberextraHttpHeadersstringgeolocationstringnetworkConditionsstringOffline · Slow 3G · Fast 3G · Slow 4G · Fast 4GuserAgentstringviewportstringevaluate_scriptEvaluate a JavaScript function inside the currently selected page. Returns the response as JSON, so returned values have to be JSON-serializable.4 paramsEvaluate a JavaScript function inside the currently selected page. Returns the response as JSON, so returned values have to be JSON-serializable.
argsarraydialogActionstringfilePathstringfunction*stringfillType text into an input, text area or select an option from a <select> element.3 paramsType text into an input, text area or select an option from a <select> element.
includeSnapshotbooleanuid*stringvalue*stringfill_formFill 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, passw...2 paramsFill 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, passw...
elements*arrayincludeSnapshotbooleanget_console_messageGets a console message by its ID. You can get all messages by calling list_console_messages.1 paramsGets a console message by its ID. You can get all messages by calling list_console_messages.
msgid*numberget_network_requestGets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.3 paramsGets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.
reqidnumberrequestFilePathstringresponseFilePathstringhandle_dialogIf a browser dialog was opened, use this command to handle it2 paramsIf a browser dialog was opened, use this command to handle it
action*stringaccept · dismisspromptTextstringhoverHover over the provided element2 paramsHover over the provided element
includeSnapshotbooleanuid*stringlighthouse_auditGet Lighthouse score and reports for accessibility, SEO, best practices, and agentic browsing. This excludes performance. For performance audits, run performance_start_trace3 paramsGet Lighthouse score and reports for accessibility, SEO, best practices, and agentic browsing. This excludes performance. For performance audits, run performance_start_trace
devicestringdesktop · mobiledefault: desktopmodestringnavigation · snapshotdefault: navigationoutputDirPathstringlist_console_messagesList all console messages for the currently selected page since the last navigation.5 paramsList all console messages for the currently selected page since the last navigation.
includePreservedMessagesbooleanpageIdxintegerpageSizeintegerserviceWorkerIdstringtypesarraylist_network_requestsList all requests for the currently selected page since the last navigation.4 paramsList all requests for the currently selected page since the last navigation.
includePreservedRequestsbooleanpageIdxintegerpageSizeintegerresourceTypesarraylist_pagesGet a list of pages open in the browser.Get a list of pages open in the browser.
No parameters — call it with no arguments.
navigate_pageGo to a URL, or back, forward, or reload. Use project URL if not specified otherwise.6 paramsGo to a URL, or back, forward, or reload. Use project URL if not specified otherwise.
handleBeforeUnloadstringaccept · declineignoreCachebooleaninitScriptstringtimeoutintegertypestringurl · back · forward · reloadurlstringnew_pageOpen a new tab and load a URL. Use project URL if not specified otherwise.4 paramsOpen a new tab and load a URL. Use project URL if not specified otherwise.
backgroundbooleanisolatedContextstringtimeoutintegerurl*stringperformance_analyze_insightProvides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording.2 paramsProvides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording.
insightName*stringinsightSetId*stringperformance_start_traceStart a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed.3 paramsStart a performance trace on the selected webpage. Use to find frontend performance issues, Core Web Vitals (LCP, INP, CLS), and improve page load speed.
autoStopbooleanfilePathstringreloadbooleanperformance_stop_traceStop the active performance trace recording on the selected webpage.1 paramsStop the active performance trace recording on the selected webpage.
filePathstringpress_keyPress 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).2 paramsPress 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).
includeSnapshotbooleankey*stringresize_pageResizes the selected page's window so that the page has specified dimension2 paramsResizes the selected page's window so that the page has specified dimension
height*numberwidth*numberselect_pageSelect a page as a context for future tool calls.2 paramsSelect a page as a context for future tool calls.
bringToFrontbooleanpageId*numbertake_heapsnapshotCapture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks.1 paramsCapture a heap snapshot of the currently selected page. Use to analyze the memory distribution of JavaScript objects and debug memory leaks.
filePath*stringtake_screenshotTake a screenshot of the page or element.5 paramsTake a screenshot of the page or element.
filePathstringformatstringpng · jpeg · webpdefault: pngfullPagebooleanqualitynumberuidstringtake_snapshotTake a text snapshot of the currently selected 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...2 paramsTake a text snapshot of the currently selected 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...
filePathstringverbosebooleantype_textType text using keyboard into a previously focused input2 paramsType text using keyboard into a previously focused input
submitKeystringtext*stringupload_fileUpload a file through a provided element.3 paramsUpload a file through a provided element.
filePath*stringincludeSnapshotbooleanuid*stringwait_forWait for the specified text to appear on the selected page.2 paramsWait for the specified text to appear on the selected page.
text*arraytimeoutintegerChrome 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 acts as a Model-Context-Protocol
(MCP) server, giving your AI coding assistant access to the full power of
Chrome DevTools for reliable automation, in-depth debugging, and performance analysis.
A CLI is also provided for use without MCP.
Tool reference | Changelog | Contributing | Troubleshooting | Design Principles
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.
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:
"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.
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.
Add the following config to your MCP client:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest"]
}
}
}
[!NOTE] Using
chrome-devtools-mcp@latestensures that your MCP client will always use the latest version of the Chrome DevTools MCP server.
If you are interested in doing only basic browser tasks, use the --slim mode:
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": ["-y", "chrome-devtools-mcp@latest", "--slim", "--headless"]
}
}
}
See Slim tool reference.
For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide.
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.
If you run into any issues, checkout our troubleshooting guide. See the full Tool Reference for a complete list of all supported MCP capabilities.
Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.
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.
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.