Network.enable timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.

[yanglijun05]

Description of the bug

Network.enable timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.

Reproduction

No response

Expectation

enable MCP

MCP configuration

"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"chrome-devtools-mcp@latest",
"--autoConnect",
"--usageStatistics=false",
"--performanceCrux=false"
]
}
}

Chrome DevTools MCP version

0.19.0

Chrome version

No response

Coding agent version

No response

Model version

No response

Chat log

No response

Node version

v20.19.2

Operating system

macOS

Extra checklist

• I want to provide a PR to fix this bug

[zyzyzyryxy]

Hello, thank you for your time reporting the issue.

To properly triage it, we need more details on circumstances you encountered this issue:

• when the error happened? Was it during chrome-devtools-mcp connecting to Chrome?
• How many tabs did you have open in the Chrome instance you were trying to connect to?
• Was this your local Chrome or a remote configuration?
• was the system under a heavy load at the moment?
• Does this error happen frequently in your setup?

One solution that comes to mind would be to add a flag to customize protocolTimeout, but that would be a feature request and we need answers to the above to plan it correctly.

[grexzen]

This error is happening all the time now. It was working at some point, but today every call shows that same error.

Chrome is local, no heavy load anything, something happened that now all calls are blocked.

[zyzyzyryxy]

I have no issues connecting to Chrome using gemini-cli and setup specified in the description. If it happens consistently for you, please provide your Chrome version and share logs from the MCP server by following instructions in https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/troubleshooting.md#debugging