Cannot connect to the Chrome-devtools mcp server using the gemini-cli.

[PerryFinn]

Describe the bug
After I installed the mcp package using the README instructions for gemini-cli, I restarted gemini-cli and tried to use it with the command:

gemini -s

However, I found that mcp was unable to connect.

On the contrary, when I use the Cursor and register the mcp with it, and then enable the agent mode, entering the test prompt allows the website to be opened normally for performance analysis.

text prompt

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

To Reproduce
Steps to reproduce the behavior:

1. Install the latest version of gemini-cli. brew install gemini-cli
2. Add that MCP to gemini-cli. gemini mcp add -s user chrome-devtools npx chrome-devtools-mcp@latest
3. Start gemini-cli. gemini -s
4. Press Ctrl+O to view the details of the error.

Expected behavior
The expected behavior is that when the gemini-cli is launched, there should be no error messages, and when the test prompt is entered, the Chrome browser should open successfully for use.

Chrome version: 140.0.7339.214
Coding agent version: gemini-cli@0.6.1
Model version: gemini-2.5-pro
Node version: 22.16.0

Screenshots

type /mcp

Chat log
The full log of the chat with your coding agent.

[jenilsoni-ai]

If running using a sandboxed environment is not a necessity try using gemini command directly instead of gemini -s and then try using the MCP server

[PerryFinn]

As can be seen in the image, the connection is still closed, which is really strange.

[jenilsoni-ai]

Inside your 'C:\Users\userrname\AppData\Roaming\Code\User' check the mcp.json file or in VS Code, click extensions and you should see something similar to what is shown in the below given image :-

[PerryFinn]

For gemini-cli, the MCP configuration is stored by default in a file called ~/.gemini/settings.json on my computer.

For a Cursor that is working properly, its status is green, and the configuration of chrome-devtools mcp is always done according to the README instructions.🤔

Maybe you’ve noticed that I’m not using npx but bunx in the command; however, both are useful. On the contrary, if I use bunx within gemini-cli, I get a completely different error message. That’s why I use npx in gemini-cli.

By the way, I forgot to mention what version of Node.js I’m using:

node -v # 22.16.0

[OrKoN]

It is a known limitation that the MCP server cannot start Chrome if it is sandboxed https://github.com/ChromeDevTools/chrome-devtools-mcp?tab=readme-ov-file#known-limitations

[aborruso]

It is a known limitation that the MCP server cannot start Chrome if it is sandboxed ChromeDevTools/chrome-devtools-mcp#known-limitations

Then it's not possible to use it in gemini cli? If is it possible, how to do it? Is there some documentation?

Thank you

[OrKoN]

It is a known limitation that the MCP server cannot start Chrome if it is sandboxed ChromeDevTools/chrome-devtools-mcp#known-limitations

Then it's not possible to use it in gemini cli? If is it possible, how to do it? Is there some documentation?

Thank you

it is possible to use chrome-devtools-mcp with gemini-cli as documented in the readme, just not with the sandbox feature turned on in the gemini-cli. If you want to use the sandbox feature, then you need to start Chrome manually and connect using --browserUrl as documented in the link.

[aborruso]

it is possible to use chrome-devtools-mcp with gemini-cli as documented in the readme, just not with the sandbox feature turned on in the gemini-cli. If you want to use the sandbox feature, then you need to start Chrome manually and connect using --browserUrl as documented in the link.

Thank you.

When I start gemini cli, I have always "🔴 chrome-devtools - Disconnected (0 tools cached)"

What command can I run to see if it works? Whatever I type, it always suggests using playwright.
If I say "Use chrome-devtools MCP," it replies, "I don't have a tool called chrome-devtools MCP."

Thank you

[OrKoN]

You can try npx chrome-devtools-mcp@latest --version to make sure it runs outside of gemini-cli.

[aborruso]

You can try npx chrome-devtools-mcp@latest --version to make sure it runs outside of gemini-cli.

Solved

`chrome-devtools-mcp` does not support Node v20.17.0. Please upgrade to Node 22.12.0 or newer.

I don't know if it's written in the installation guide. If it's not there, it should be added.

Thank you

[sebastianbenz]

Closing as this issues seems to be resolved