Chrome DevTools MCP (2025)

We shipped an enhancement to the Chrome DevTools MCP server that many of our
users have been asking for: the ability for coding agents to directly connect to
active browser sessions.

With this enhancement, coding agents are able to:
The auto connection feature is an addition to the existing ways for the Chrome
DevTools MCP to connect to a Chrome instance.

Note that you can still:
We've added a new feature to Chrome M144 (currently in Beta) that allows the
Chrome DevTools MCP server to request a remote debugging connection.

This new
flow builds on top of theexisting remote debugging capabilities of
Chrome.

By default, remote
debugging connections are disabled in Chrome.

Developers have to explicitly
enable the feature first by going tochrome://inspect#remote-debugging.

When the Chrome DevTools MCP server is configured with the--autoConnectoption, the MCP server will connect to an active Chrome instance and request a
remote debugging session.

To avoid misuse by malicious actors, every time the
Chrome DevTools MCP server requests a remote debugging session, Chrome will show
a dialog to the user and ask for their permission to allow the remote debugging
session.

In addition to that, while a debugging session is active, Chrome
displays the "Chrome is being controlled by automated test software" banner at
the top.

To use the new remote debugging capabilities.

You have to first enable remote
debugging in Chrome and then configure the Chrome DevTools MCP server to use the
new auto connection feature.

In Chrome (>=144), do the following to set up remote debugging:
To connect thechrome-devtools-mcpserver to the running Chrome instance, use--autoConnectcommand line argument for the MCP server set.

The following code snippet is an example configuration for gemini-cli:
Now open gemini-cli and run the following prompt:
The Chrome DevTools MCP server will try to connect to your running Chrome
instance.

It shows a dialog asking for user permission:
ClickingAllowresults in the Chrome DevTools MCP server openingdevelopers.chrome.comand taking a performance
trace.

For full instructions, check out theREADME on
GitHub.

Being able to connect to a live Chrome instance means you don't have to choose
between automation and manual control.

You can use DevTools yourself or hand
over a debugging task to your coding agent.

If you discover a problem on your
website, you can open DevTools to take a look to identify the element that's
causing the issue.

If you want your coding agent to fix the issue, you can now
do so with Chrome DevTools MCP Server.

You can select the element in the
Elements panel and ask the coding agent to investigate the issue.

The same also works for the Network panel.

You can select a network request and
ask your coding agent to investigate it.

But this is just a first step.

We plan to incrementally expose more and more
panel data to coding agents through the Chrome DevTools MCP Server.

Stay tuned!