MCP server and CLI for Brave DevTools
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Full Chrome DevTools MCP parity, rebuilt for Brave.

brave-mcp gives Claude Code, Codex, Cursor, OpenCode, and other MCP clients direct access to Brave for browser automation, network and console debugging, performance analysis, screenshots, accessibility inspection, and memory profiling. A standalone brave-devtools CLI is included too.
Restart your client, then try this prompt:
Open my app in Brave. Find console errors and failed network requests, inspect the accessibility tree, run Lighthouse, and explain the highest-impact issue.
| Capability | brave-mcp | chrome-devtools-mcp |
|---|---|---|
| Browser launched and discovered natively | Brave Release, Beta, and Nightly | Chrome Stable, Beta, Dev, and Canary |
| Attach to an existing browser | Brave profiles, HTTP, or WebSocket | Chrome profiles, HTTP, or WebSocket |
| Upstream DevTools features | Full parity; currently 0 commits behind | Source implementation |
| Usage telemetry | Disabled by default | Enabled by default |
| Standalone CLI | brave-devtools | chrome-devtools |
Use Chrome DevTools MCP when your target browser is Chrome. Use brave-mcp when your target browser is Brave and you want Brave-native discovery, profiles, channels, naming, and privacy defaults without giving up upstream features.
brave-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.
brave-mcp officially supports the current Brave release. Beta and Nightly channels can be selected explicitly.
Performance tools may send trace URLs to the Google CrUX API to fetch real-user
experience data. This helps provide a holistic performance picture by
presenting field data alongside lab data. This data is collected by the Chrome
User Experience Report (CrUX). To disable
this, run with the --no-performance-crux flag.
Usage statistics collection is disabled by default in this fork. It can be enabled explicitly with --usage-statistics, which uses the upstream Google Clearcut implementation:
When enabled, Google handles this data in accordance with the Google Privacy Policy. Collection remains disabled if BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS or CI is set.
By default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available.
You can disable these update checks by setting BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS.
Add the following config to your MCP client:
[!NOTE] Using
brave-mcp@latestensures that your MCP client will always use the latest version of the Brave DevTools MCP server.
If you are interested in doing only basic browser tasks, use the --slim mode:
See Slim tool reference.
To use the Brave DevTools MCP server follow the instructions from Antigravity's docs to install a custom MCP server. Add the following config to the MCP servers config:
This will make the Brave DevTools MCP server automatically connect to the browser that Antigravity is using. If you are not using port 9222, make sure to adjust accordingly.
Brave DevTools MCP will not start the browser instance automatically using this approach because the Brave DevTools MCP server connects to Antigravity's built-in browser. If the browser is not already running, you have to start it first by clicking the Chrome icon at the top right corner.
Follow the IBM Bob MCP guide and add the Brave DevTools MCP server to your Bob MCP configuration. Use the global config (~/.bob/mcp.json) to apply it across all workspaces, or a project config (.bob/mcp.json) to scope it to one project:
You can edit these files from Bob panel β Settings β MCP β Edit Global MCP (or Edit Project MCP). Bob hot-reloads on save. Once the server appears in the MCP tab, switch to the π Browser Dev mode to get guided browser debugging directly in Bob.
Install via CLI (MCP only)
Use the Claude Code CLI to add the Brave DevTools MCP server (guide):
Install as a Plugin (MCP + Skills)
[!NOTE] If you already had Brave DevTools MCP installed previously for Claude Code, make sure to remove it first from your installation and configuration files.
To install Brave DevTools MCP with skills, add the marketplace registry in Claude Code:
Then, install the plugin:
Restart Claude Code to have the MCP server and skills load (check with /skills).
[!TIP] If the plugin installation fails with a
Failed to clone repositoryerror (e.g., HTTPS connectivity issues behind a corporate firewall), see the troubleshooting guide for workarounds, or use the CLI installation method above instead.
On Windows 11
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/brave-devtools-mcp)<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>