brave-devtools-mcp

Brave DevTools MCP

Modified version of chrome-devtools-mcp without telemetry data and adapted to work with brave. Plug and play as it is just a Chromium browser.

Fork of chrome-devtools-mcp, adapted for Brave Browser.

Disclaimers

brave-devtools-mcp 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.

Requirements

• Node.js v20.19 or a newer latest maintenance LTS version.
• Brave Browser current stable version or newer.
• npm.

Installation

Since brave-devtools-mcp is not published to the public npm registry, you need to install it manually from this repository.

1. Clone the repository

git clone https://github.com/381sm016/brave-devtools-mcp.git
cd brave-devtools-mcp

2. Install dependencies

npm install

3. (Optional) Build / prepare

If the project uses a build step (e.g. TypeScript), run it here. If not, you can skip this.

npm run build

4. Decide how you want to reference the server

You have two main options:

1. Use a local path directly (recommended for development)
2. Use a global install from the cloned repo

Option A: Use a local path directly

Most MCP clients let you point command at a local node or npm and then pass a relative path to the repo’s entry point.

Example (generic):

{
  "mcpServers": {
    "brave-devtools": {
      "command": "node",
      "args": [
        "/absolute/path/to/brave-devtools-mcp/dist/index.js"
      ]
    }
  }
}

Adjust the path to whatever the actual entry file is (e.g. bin/brave-devtools-mcp.js, dist/index.js, etc).

Option B: Global install from the cloned repo

From inside the cloned repo:

npm install -g .

This will make a brave-devtools-mcp binary available on your PATH (assuming the project exposes one). You can then use just brave-devtools-mcp as the command in your MCP clients.

brave-devtools-mcp --help

Getting started

After manual installation, configure your MCP client to use the locally installed brave-devtools-mcp rather than npx / npm.

MCP Client configuration

Below are per–agent examples using manual/local installation.

Replace /absolute/path/to/brave-devtools-mcp and any script paths with the actual location on your system. If you installed globally with npm install -g . and have a brave-devtools-mcp binary, you can use "command": "brave-devtools-mcp" and omit the path.

claude mcp add brave-devtools --scope user brave-devtools-mcp

claude mcp add brave-devtools --scope user node /absolute/path/to/brave-devtools-mcp/dist/index.js

{
  "mcpServers": {
    "brave-devtools": {
      "command": "brave-devtools-mcp",
      "args": []
    }
  }
}

{
  "mcpServers": {
    "brave-devtools": {
      "command": "node",
      "args": ["/absolute/path/to/brave-devtools-mcp/dist/index.js"]
    }
  }
}

{
  "mcpServers": {
    "brave-devtools": {
      "command": "brave-devtools-mcp",
      "args": []
    }
  }
}

{
  "mcpServers": {
    "brave-devtools": {
      "command": "node",
      "args": ["/absolute/path/to/brave-devtools-mcp/dist/index.js"]
    }
  }
}

{
  "mcpServers": {
    "brave-devtools": {
      "command": "brave-devtools-mcp",
      "args": []
    }
  }
}

{
  "mcpServers": {
    "brave-devtools": {
      "command": "node",
      "args": ["/absolute/path/to/brave-devtools-mcp/dist/index.js"]
    }
  }
}