Log inSubmit server
Brave DevTools MCP logo

Brave DevTools MCP

Automates and debugs Brave with tools for network, console, performance, screenshots, accessibility, and memory.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Brave DevTools MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "brave-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brave-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Brave DevTools MCP MCP server connects MCP clients to Brave for browser automation, debugging, and performance analysis. It uses Brave remote debugging or launches an isolated Brave profile, with Puppeteer handling automation and Chrome DevTools components providing traces and diagnostics. Reach for it when an agent needs to inspect a Brave session, diagnose web applications, or automate browser tasks while retaining Brave-specific channels and profiles.

Use cases

  • Debug console errors and failed network requests
  • Automate signed-in Brave browser sessions
  • Run performance traces and Lighthouse analysis
  • Inspect accessibility trees and screenshots
  • Profile memory usage in Brave

Key features

  • Brave browser automation
  • Console and network debugging
  • Performance tracing and Lighthouse analysis
  • Accessibility inspection
  • Screenshots and memory profiling
  • Dedicated or existing browser profiles

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · brave-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars44Stargazers on the source repository.
Last commit8d agoMost recent push to the default branch.

How Brave DevTools MCP works

What Brave DevTools MCP does

Brave DevTools MCP MCP server gives MCP clients access to a Brave browser instance. Agents can automate browser actions, inspect pages, review console messages, analyze network requests, capture screenshots, inspect accessibility information, and run performance analysis. The package also includes a standalone brave-devtools command-line interface.

The project is intended for developers whose target browser is Brave rather than Chrome. It follows the upstream Chrome DevTools MCP feature set while adding Brave-specific browser discovery, profiles, release channels, and naming. Current Brave release is officially supported; Beta and Nightly can be selected explicitly.

How it works

The server can attach to an existing Brave session through remote debugging, HTTP, or WebSocket connections. With --autoConnect, it uses the Brave browser already open on the machine, including its real tabs and signed-in sessions. Without that option, it starts Brave with a dedicated profile when a browser-dependent tool is first used.

Puppeteer performs browser automation and waits for action results. Chrome DevTools components record traces and extract performance insights. Performance analysis may combine lab trace data with field information from the Google CrUX API. Disable that lookup with --no-performance-crux if trace URLs should not be sent for CrUX data.

Setup and configuration

Install with Node.js LTS, npm, and the current Brave release or newer. Before using --autoConnect, open brave://inspect/#remote-debugging in Brave and enable remote debugging for the browser instance. Brave asks for permission when the client first connects; approve the request to allow access.

A typical MCP configuration runs npx -y brave-mcp@latest --autoConnect. The default connection targets Brave Release. Use --channel beta or --channel nightly for another supported channel. Omitting --autoConnect keeps agent activity in a separate Brave profile. The --slim option provides a reduced tool set for basic browser tasks and can be combined with --headless.

Optional settings include --isolated, persistent user-data directories, WebSocket connections, concurrent sessions, and Android debugging. Usage statistics are off by default. They can be enabled with --usage-statistics, but collection remains disabled when BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI is set. Set BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS to stop periodic npm update checks.

Tools and capabilities

Brave DevTools MCP MCP server supports capabilities for:

  • Browser navigation and automated interaction
  • Console inspection with source-mapped stack traces
  • Network request analysis
  • Screenshots
  • Accessibility-tree inspection
  • Performance tracing and Lighthouse analysis
  • Memory profiling

The full mode targets feature parity with Chrome DevTools MCP. A slim mode is available when only basic browser operations are needed. The exact tool names and parameters are documented in the project’s tool references.

Limitations and notes

The server exposes browser and DevTools content to connected MCP clients, including data they may inspect, debug, or modify. Do not use it with sensitive information that should not be shared with the client.

Official support covers the current Brave release. Beta and Nightly require explicit channel selection. Performance tools can contact the Google CrUX API unless that behavior is disabled. Update notifications are enabled by default, while usage statistics are disabled by default.

Use Chrome DevTools MCP instead when the target browser is Chrome. Choose Brave DevTools MCP MCP server when the target is Brave and Brave-native browser discovery, profiles, or channels are required.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Brave DevTools MCP

Brave DevTools MCP is an MCP server that connects MCP clients to Brave for browser automation and debugging. Its main tools cover navigation, console and network inspection, screenshots, accessibility inspection, performance tracing, Lighthouse analysis, and memory profiling. It can attach to an existing Brave session or launch a dedicated profile.

Install it through an MCP client with `npx -y brave-mcp@latest --autoConnect`. Enable remote debugging at `brave://inspect/#remote-debugging` first, then restart the client and approve Brave’s connection prompt. Node.js LTS, npm, and the current Brave release or newer are required.

Yes, Brave DevTools MCP works with Cursor through a standard MCP configuration. Add the server with Cursor’s MCP command using `npx -y brave-mcp@latest --autoConnect`, enable Brave remote debugging, and restart Cursor before using browser tools.

Use the `--autoConnect` argument after enabling remote debugging in Brave. The server then attaches to the open Brave browser, including its real tabs and signed-in sessions. Brave Release is selected by default; use `--channel beta` or `--channel nightly` for another supported channel.

Omit `--autoConnect` so the server launches Brave with a dedicated profile. The browser starts when an MCP client first calls a tool that needs it. For a reduced setup aimed at basic tasks, add `--slim`, and use `--headless` when headless operation is appropriate.

Related MCP servers

All in Browser Automation All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewBrave DevTools MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/brave-devtools-mcp?style=directory)](https://allmcps.com/mcp/brave-devtools-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/brave-devtools-mcp"><img src="https://allmcps.com/api/badge/brave-devtools-mcp?style=directory" alt="Brave DevTools MCP on AllMCPs" /></a>