chrome-devtools-mcp --autoConnect times out on every tool call with Chrome 144

4 answers

• Best answerAgentArmor teamTeam1d ago

  Status: the issue is closed as completed, but this thread does not show a code fix for the timeout itself. Maintainers confirmed that --autoConnect support landed in the Chrome 144 branch (initially it landed in 145), so Chrome 144 is the expected minimum, and the docs were updated to match.

  The config used in the thread:

  jsonCopy to clipboard

  "chrome-devtools": {
    "type": "local",
    "command": ["npx", "-y", "chrome-devtools-mcp@latest", "--autoConnect", "--channel=stable"]
  }
  

  --channel=beta and no channel flag were also tried.

  What the thread established:

  1. The accept dialog ("allow automated testing?") appearing means auto-connect itself works; the timeout happens on the tool call after the connection. After clicking allow, the reporter got McpError: MCP error -32001: Request timed out in both Warp and the VS Code terminal.
  2. A maintainer could not reproduce with the MCP inspector and suggested checking which tool call times out, whether the client uses the standard 60s timeout, extensions, open tabs, and capturing debug logs from the project's troubleshooting doc.
  3. A clean test still reproduced: brand-new Chrome profile with no extensions and one chrome://newtab tab, then npx @modelcontextprotocol/inspector npx chrome-devtools-mcp@latest --auto-connect, Connect, List tools, call list_pages. Result: Network.enable timed out after a few minutes.
  4. Two users reported having multiple Chrome profiles; the maintainer asked whether that was the case, but the thread never confirms it as the cause.

  Note: the DevTools Protocol Monitor pane does not show MCP traffic, so it will not help debug this.

  General advice: --autoConnect attaches to your real Chrome profile with remote debugging enabled, so only enable it on a machine you control and disable it when done.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

  What @ProjectBetelgeuse tried on GitHub (Didn't work)

  The reporter set up chrome-devtools-mcp v0.13.0 with opencode, tried --autoConnect with --channel=stable, --channel=beta, and no channel flag on Chrome 144 with remote debugging enabled. The server printed chrome-devtools_new_page [url=https://developers.chrome.com] but never opened a page and timed out.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/775 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

  What @ProjectBetelgeuse tried on GitHub (Didn't work)

  The reporter confirmed the exact npx command, enabled "Allow remote debugging for this browser instance", clicked allow on the automated-test dialog, and then got McpError: MCP error -32001: Request timed out. The same failure happened in both Warp and the VS Code terminal.

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/775#issuecomment-3757800011 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam1d ago

  What @yotahk tried on GitHub (Didn't work)

  A user tested with a brand-new Chrome profile with no extensions and one chrome://newtab tab, running npx @modelcontextprotocol/inspector npx chrome-devtools-mcp@latest --auto-connect, then calling list_pages. It failed after a few minutes with Network.enable timed out. Increase the 'protocolTimeout' setting....

  Source: https://github.com/ChromeDevTools/chrome-devtools-mcp/issues/775#issuecomment-3762837801 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport