chrome-devtools-mcp-for-brave lets your coding agent (such as Gemini, Claude, Cursor or Copilot) control and inspect a live Brave browser. It acts as a Model-Context-Protocol (MCP) server, giving your AI coding assistant access to the full power of Brave DevTools for reliable automation, in-depth debugging, and performance analysis.

1. Set Up Brave to open your default browser profile as the browser used for MCP to debug ( so you havea all your passwords and plugins and such )

• Close all Brave instanes
• Copy and run this in terminal / cli etc

/Applications/Brave\ Browser.app/Contents/MacOS/Brave\ Browser \
  --remote-debugging-port=9222 \
  --user-data-dir="$HOME/Library/Application Support/BraveSoftware/Brave-Browser" \
  --profile-directory="Default"

2. Set up MCP with correct args for using this browser window

{
  "mcpServers": {
    "brave-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp-for-brave@latest",
        "--browserUrl",
        "http://127.0.0.1:9222"
      ]
    }
  }
}

• Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights.
• Advanced browser debugging: Analyze network requests, take screenshots and check the browser console.
• Reliable automation. Uses puppeteer to automate actions in Brave and automatically wait for action results.
• Brave-optimized: Designed specifically for Brave browser with automatic detection.

chrome-devtools-mcp-for-brave exposes content of the browser instance to the MCP clients allowing them to inspect, debug, and modify any data in the browser or DevTools. Avoid sharing sensitive or personal information that you don't want to share with MCP clients.

• Node.js 22.12.0 or newer.
• Brave Browser current stable version or newer.
• npm.

Add the following config to your MCP client:

{
  "mcpServers": {
    "brave-devtools": {
      "command": "npx",
      "args": ["chrome-devtools-mcp-for-brave@latest"]
    }
  }
}

claude mcp add brave-devtools npx chrome-devtools-mcp-for-brave@latest

codex mcp add brave-devtools -- npx chrome-devtools-mcp-for-brave@latest

code --add-mcp '{"name":"brave-devtools","command":"npx","args":["chrome-devtools-mcp-for-brave@latest"]}'

gemini mcp add brave-devtools npx chrome-devtools-mcp-for-brave@latest

gemini mcp add -s user brave-devtools npx chrome-devtools-mcp-for-brave@latest

Enter the following prompt in your MCP Client to check if everything is working:

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

Your MCP client should open the browser and record a performance trace.

• Input automation (7 tools)
  • click
  • drag
  • fill
  • fill_form
  • handle_dialog
  • hover
  • upload_file
• Navigation automation (7 tools)
  • close_page
  • list_pages
  • navigate_page
  • navigate_page_history
  • new_page
  • select_page
  • wait_for
• Emulation (3 tools)
  • emulate_cpu
  • emulate_network
  • resize_page
• Performance (3 tools)
  • performance_analyze_insight
  • performance_start_trace
  • performance_stop_trace
• Network (2 tools)
  • get_network_request
  • list_network_requests
• Debugging (4 tools)
  • evaluate_script
  • list_console_messages
  • take_screenshot
  • take_snapshot

The DevTools MCP server supports the following configuration options:

• --browserUrl, -u Connect to a running Brave instance using port forwarding. For more details see: https://developer.chrome.com/docs/devtools/remote-debugging/local-server.

  • Type: string

• --headless Whether to run in headless (no UI) mode.

  • Type: boolean
  • Default: false

• --executablePath, -e Path to custom Brave executable.

  • Type: string

• --isolated If specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed.

  • Type: boolean
  • Default: false

• --logFile Path to a file to write debug logs to. Set the env variable DEBUG to * to enable verbose logs. Useful for submitting bug reports.

  • Type: string

Pass them via the args property in the JSON configuration. For example:

{
  "mcpServers": {
    "brave-devtools": {
      "command": "npx",
      "args": [
        "chrome-devtools-mcp-for-brave@latest",
        "--headless=true",
        "--isolated=true"
      ]
    }
  }
}

You can also run npx chrome-devtools-mcp-for-brave@latest --help to see all available configuration options.

The MCP server uses the following user data directory for Brave:

• Linux / MacOS: $HOME/.cache/brave-devtools-mcp/brave-profile
• Windows: %HOMEPATH%/.cache/brave-devtools-mcp/brave-profile

The user data directory is not cleared between runs and shared across all instances of the MCP server. Set the isolated option to true to use a temporary user data dir instead which will be cleared automatically after the browser is closed.

Some MCP clients allow sandboxing the MCP server using macOS Seatbelt or Linux containers. If sandboxes are enabled, the MCP server is not able to start Brave as it requires permissions to create its own sandboxes. As a workaround, either disable sandboxing for the MCP server in your MCP client or use --browserUrl to connect to a Brave instance that you start manually outside of the MCP client sandbox.