Node.js and Chrome Version Compatibility Requirements for MCP: Complete Setup Guide

Chrome DevTools MCP requires Node.js v20.19 or later (including v22.x LTS) and a current stable Chrome browser, with Chrome 144+ needed for automatic connection features.

The Chrome DevTools MCP server enables AI assistants to interact directly with browser internals through the Model Context Protocol. Understanding the Node.js and Chrome version compatibility requirements for MCP ensures reliable installation and prevents runtime errors when connecting to target browsers. The ChromeDevTools/chrome-devtools-mcp repository explicitly defines these constraints in its configuration files and documentation.

Minimum Node.js Version Requirements for Chrome DevTools MCP

The server enforces strict Node.js version constraints through multiple mechanisms to ensure compatibility with modern JavaScript features and security patches.

package.json Engine Constraints

In package.json, the engines field specifies acceptable Node.js versions:

{
  "engines": {
    "node": "^20.19.0 || ^22.12.0 || >=23"
  }
}

This configuration mandates Node.js v20.19.0 as the absolute minimum, while explicitly supporting the v22.x LTS line and any future versions 23 and above. Running npm install with an incompatible Node version will trigger a warning or error depending on your npm configuration.

Development Version Pinning with .nvmrc

For contributors and developers working directly with the repository, the .nvmrc file at the root pins the development environment to Node.js v22:

# .nvmrc

v22

Executing nvm use in the project directory automatically switches to Node.js 22, ensuring consistency across development machines and CI/CD pipelines. This aligns with the repository's testing infrastructure and prevents version drift during local development.

Chrome Browser Compatibility Requirements

While Node.js powers the server runtime, the Chrome DevTools MCP requires specific browser versions to establish debugging connections and utilize advanced features.

Base Stable Channel Requirement

According to the README.md requirements section, MCP requires any current stable Chrome browser. The server communicates with Chrome through the Chrome DevTools Protocol (CDP), which maintains backward compatibility across recent stable releases.

To verify your Chrome installation meets this requirement:

# macOS Chrome version check

"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --version

# Linux

google-chrome --version

# Windows (PowerShell)

(Get-Item (Get-Command chrome).Source).VersionInfo.FileVersion

The output should indicate a stable channel release (e.g., Chrome 127.0.6533.119 or later).

Chrome 144+ for Automatic Connection Features

The README.md automatic connection section specifies an additional requirement for specific functionality: Chrome 144 or higher enables the --auto-connect feature, allowing MCP to attach to already-running browser instances without manual debugging port configuration.

To utilize automatic connection:

# Requires Chrome 144+ with remote debugging enabled

npx chrome-devtools-mcp@latest --auto-connect

This feature inspects chrome://inspect/#remote-debugging to discover attachable targets. Attempting to use --auto-connect with Chrome versions below 144 will result in connection failures or fallback to manual port specification.

Verifying Your Environment Setup

Before launching the MCP server, validate both Node.js and Chrome installations against the compatibility matrix:

# Check Node.js version (must be >= 20.19.0)

node --version

# Verify npm respects engine constraints

npm config get engine-strict

# Check Chrome version (macOS example)

"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --version

If node --version returns v18.x or earlier, upgrade using nvm install 20 or download the LTS installer from nodejs.org. For Chrome, ensure automatic updates are enabled or manually download the current stable release from the official Chrome distribution channels.

Troubleshooting Compatibility Issues

When encountering startup errors, consult the docs/troubleshooting.md file for version-specific guidance. Common issues include:

• Engine mismatch errors: Occur when running npm install with Node.js versions below v20.19.0. Resolve by switching to a compatible Node version using nvm use 20 or nvm use 22.
• Protocol connection timeouts: Usually indicate Chrome version incompatibility or missing remote debugging flags. Verify Chrome is v127+ (stable) and launched with --remote-debugging-port=9222.
• Auto-connect failures: Specifically require Chrome 144+. Check your Chrome version and disable auto-connect if running older browser versions, manually specifying the debugging port instead.

Summary

The Chrome DevTools MCP server maintains strict runtime requirements to ensure reliable browser automation:

• Node.js v20.19.0 minimum is enforced via package.json engines, with v22.x recommended for development
• Current stable Chrome is required for basic debugging connections
• Chrome 144+ unlocks the --auto-connect feature for attaching to existing browser instances
• Configuration files including .nvmrc and package.json provide explicit version pinning for consistent deployments

Frequently Asked Questions

What is the minimum Node.js version required for Chrome DevTools MCP?

The absolute minimum Node.js version is v20.19.0, though the repository explicitly supports v22.x LTS and any version 23 or higher. This constraint is defined in the package.json engines field and enforced during npm install.

Can I use Chrome DevTools MCP with Chrome Beta or Canary?

While the documentation specifies "current stable Chrome," the MCP server uses the Chrome DevTools Protocol (CDP), which is generally compatible with Beta and Canary channels. However, automatic connection features (--auto-connect) specifically require Chrome 144+, regardless of the release channel.

Why does automatic connection require Chrome 144 or higher?

Chrome 144 introduced enhanced remote debugging discovery mechanisms that allow the MCP server to inspect chrome://inspect/#remote-debugging and attach to running browser instances without manual port configuration. Earlier Chrome versions lack this discovery capability, requiring explicit --remote-debugging-port flags and manual connection strings.

How do I check if my environment meets MCP compatibility requirements?

Run node --version to verify Node.js is v20.19.0 or later, and check your Chrome version using google-chrome --version (Linux) or /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version (macOS). Ensure Chrome is on the stable channel and version 144+ if you plan to use the --auto-connect feature.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}