# Brave DevTools MCP

> Brave DevTools MCP is an open-source MCP server for browser automation. MCP server and CLI that lets AI agents drive and debug the Brave browser. It runs locally on your machine and is started by your AI client.

- **Kind:** MCP server
- **Pricing:** Open source
- **Platforms:** CLI, macOS, Windows, Linux, self-hosted
- **Repository:** https://github.com/triuzzi/brave-devtools-mcp
- **MCP Registry name:** io.github.triuzzi/brave-mcp
- **Categories:** [browser automation](https://ai-powered.com/categories/browser-automation)
- **Listing updated:** 2026-11-18

## About

The README says this server connects MCP clients such as Claude Code, Cursor, Codex and OpenCode to a Brave browser session. Agents can then record performance traces, read network requests and console messages, take screenshots, inspect the accessibility tree and profile memory. It is a fork of Chrome DevTools MCP rebuilt to find Brave Release, Beta and Nightly natively.

The main setup option is an autoConnect flag that attaches to the Brave instance already open, including signed-in tabs, after remote debugging is enabled in brave://inspect. Without that flag, the server launches its own Brave with a dedicated profile. A reduced --slim mode exposes only basic browser tasks, and a separate brave-devtools CLI runs the same actions from a terminal.

It suits developers debugging web apps in Brave and teams building agents that need a browser. The README warns that connected clients can read and modify anything in the browser, so it should be used with care around sensitive sessions.

## Features

- **Performance trace analysis:** Records traces and extracts performance insights using Chrome DevTools tooling.
- **Network and console debugging:** Inspects network requests and browser console messages with source-mapped stack traces.
- **Attach to running Brave:** The autoConnect option attaches to the open Brave browser and its existing sessions.
- **Dedicated profile launch:** Without autoConnect, the server starts its own Brave instance with a separate profile.
- **Slim mode:** A --slim flag exposes a smaller set of tools for basic browser tasks.
- **Standalone CLI:** The brave-devtools command runs browser actions from a terminal without MCP.
- **Agent skills:** Bundled skills cover accessibility, cookies, LCP and memory leak debugging.

## Good for

- Finding console errors and failed requests in a web app running in Brave
- Running Lighthouse or performance traces from an AI coding assistant
- Auditing accessibility trees on a page an agent is viewing
- Debugging cookies and sessions in a signed-in Brave profile
- Scripting screenshots and page navigation from the command line

## Install

### Claude Code (Terminal)

```sh
claude mcp add brave-mcp -- npx -y brave-mcp
```

### Claude Desktop (claude_desktop_config.json)

```json
{
  "mcpServers": {
    "brave-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp"
      ]
    }
  }
}
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "brave-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp"
      ]
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "brave-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp"
      ]
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "brave-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp"
      ]
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "brave-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp"
      ]
    }
  }
}
```

## FAQ

### How do I connect it to my running Brave browser?

Enable remote debugging at brave://inspect/#remote-debugging, then add the server with the --autoConnect argument in your MCP client config.

### Does it need an API key or environment variables?

The registry entry lists no environment variables. Usage statistics are disabled by default.

### Which Brave channels are supported?

It attaches to Brave Release by default and can use Beta or Nightly with the --channel flag.

### Is Brave DevTools MCP free?

Yes. Brave DevTools MCP is open source, so you can use and self-host it for free.

### How do I add Brave DevTools MCP to Claude Code?

Run this command in your terminal: claude mcp add brave-mcp -- npx -y brave-mcp

### What are the best alternatives to Brave DevTools MCP?

The closest alternatives to Brave DevTools MCP are Chrome DevTools MCP, MCP Browser, MCP Browser Extension, NextCore Browser and playwright_mcp.

## Where this comes from

- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.

## Alternatives

- [Chrome DevTools MCP](https://ai-powered.com/mcp/chrome-devtools-mcp-4): Chrome DevTools MCP is an open-source MCP server for browser automation.
- [MCP Browser](https://ai-powered.com/mcp/mcp-browser-3): MCP Browser is an open-source MCP server for browser automation.
- [MCP Browser Extension](https://ai-powered.com/mcp/mcp-browser-extension): MCP Browser Extension is an open-source MCP server for browser automation.
- [NextCore Browser](https://ai-powered.com/mcp/nextcore-browser): NextCore Browser is a freemium MCP server for browser automation.
- [playwright_mcp](https://ai-powered.com/mcp/playwright-mcp-3): playwright_mcp is an open-source MCP server for browser automation.
- [Abrasio](https://ai-powered.com/mcp/abrasio): Abrasio is a freemium MCP server for browser automation.
- [Browsentic](https://ai-powered.com/mcp/browsentic): Browsentic is an open-source MCP server for browser automation.
- [Browser.lol](https://ai-powered.com/mcp/browser-lol): Browser.lol is a paid MCP server for browser automation.

---
Source: https://ai-powered.com/mcp/brave-devtools-mcp
