How to Use Chrome DevTools MCP Server with Cursor IDE

How to Use Chrome DevTools MCP Server with Cursor IDE (Without Breaking Your Regular Chrome)

If you’ve tried to connect the Chrome DevTools MCP server to Cursor IDE, you might have run into a frustrating wall: Chrome doesn’t automatically open a debugging port, and even if you force it, your existing Chrome session gets tangled up. After wrestling with this myself, I found a clean, simple solution. Let me share it with you.

What’s the problem?

The Chrome DevTools MCP server needs to talk to a Chrome instance that’s listening for debugging connections on a port (like 9222). But the Chrome you use daily isn’t started in debug mode. You could close Chrome and relaunch it with the right flags, but that kills your tabs and settings not ideal.

Even if you try to add the flags while Chrome is running, it won’t work. And using your regular profile for debugging can cause conflicts with extensions, bookmarks, and logged in sessions.

The solution: a separate Chrome instance just for MCP

We’ll launch a second Chrome window that:

• Runs completely isolated from your everyday Chrome (separate user data directory)
• Opens a remote debugging port (9222) that the MCP server can connect to
• Stays alive while you work in Cursor

No extensions, no cookies, no interference. Perfect for automated testing or just inspecting your code’s runtime.

Step-by-step guide (Windows)

Note: I’m using Windows here. For macOS/Linux, see the alternative commands at the end.

1. Launch a debug‑ready Chrome window

Open a Command Prompt (or PowerShell) and run this single command:

"C:\Program Files\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 --user-data-dir="C:\Temp\chrome-debug-profile"

What it does:

• --remote-debugging-port=9222 opens the debug port for MCP to connect
• --user-data-dir="C:\Temp\chrome-debug-profile" creates a fresh, temporary profile that won’t touch your normal Chrome data

A new Chrome window will pop up. It’ll look bare – no extensions, no bookmarks, no history. Keep this window open while you use Cursor.

2. Configure Cursor to use the running Chrome

In Cursor, open your MCP configuration. You can find it under File > Preferences > MCP Servers (or by editing ~/.cursor/mcp.json directly).

Add (or replace) the Chrome DevTools entry:

{
  "mcpServers": {
    "chrome-devtools": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest",
        "--browser-url=http://127.0.0.1:9222"
      ]
    }
  }
}

The key part is --browser-url=http://127.0.0.1:9222 – this tells the MCP server to connect to the Chrome instance we just launched, instead of trying to launch its own.

3. Restart Cursor (or reload MCP)

After saving the config, restart Cursor or manually reload the MCP servers from the command palette (Reload MCP Servers). You should now be able to use tools like take screenshot, navigate page, evaluate script, etc.

For macOS users

Launch a separate Chrome instance from Terminal:

"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --remote-debugging-port=9222 --user-data-dir="$HOME/temp-chrome-debug"

For Linux users

google-chrome --remote-debugging-port=9222 --user-data-dir="/tmp/chrome-debug-profile"

The Cursor config stays exactly the same across all OSes.

Why this approach rocks

• No interference Your main Chrome profile (bookmarks, passwords, extensions) stays untouched.
• Works alongside Cursor You can run the debug Chrome window in the background and close it when you’re done.
• No admin rights required Uses standard Chrome flags and a local temp folder.
• You control the lifecycle Launch the debug window only when you need it.

One small gotcha

If you close the debug Chrome window, the MCP server will lose its connection. Just re run the command to start a fresh one. And if you ever see “port already in use”, it means you have another Chrome instance occupying 9222 either close it or change the port number in both the launch command and the Cursor config.

Wrapping up

Getting Chrome DevTools MCP to work with Cursor IDE doesn’t have to be a headache. With a separate debug instance and a simple config tweak, you can inspect, automate, and debug your web apps right from Cursor – while keeping your personal Chrome session safe and sound.

I hope this saves you the hours I lost figuring it out. If you found it helpful, give it a like or share it with someone who’s wrestling with MCP and Chrome.

Have you tried other MCP servers with Cursor? Let me know in the comments I’m always looking for cool integrations.