npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

brave-mcp

v1.12.0

Published

MCP server and CLI for Brave DevTools

Readme

Brave DevTools for agents

Full Chrome DevTools MCP parity, rebuilt for Brave.

CI npm npm downloads MCP Registry npm provenance upstream license

Brave DevTools MCP: 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.

Install in one command

The commands below use --autoConnect, which attaches brave-mcp to the Brave you already have open, so the agent works with your real tabs and signed-in sessions. Enable it once: open brave://inspect/#remote-debugging in Brave and check Allow remote debugging for this browser instance. Brave keeps this setting across restarts.

Claude Code

claude mcp add brave-devtools --scope user -- npx -y brave-mcp@latest --autoConnect

Cursor

cursor --add-mcp '{"name":"brave-devtools","command":"npx","args":["-y","brave-mcp@latest","--autoConnect"]}'

Codex

codex mcp add brave-devtools -- npx -y brave-mcp@latest --autoConnect

OpenCode

opencode mcp add brave-devtools -- npx -y brave-mcp@latest --autoConnect

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.

When the agent connects, Brave asks for permission. Click Allow.

--autoConnect attaches to Brave Release unless you add --channel beta or --channel nightly. To keep the agent out of your everyday browser, leave out --autoConnect: the server then launches its own Brave with a dedicated profile.

Why use this instead of Chrome DevTools MCP?

| 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.

Tool reference | CLI | Skills | Changelog | Contributing | Troubleshooting | Design principles

Key features

  • Get performance insights: Uses Chrome DevTools to record traces and extract actionable performance insights.
  • Advanced browser debugging: Analyze network requests, take screenshots and check browser console messages (with source-mapped stack traces).
  • Reliable automation. Uses puppeteer to automate actions in Brave and automatically wait for action results.

Disclaimers

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

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:

"args": ["-y", "brave-mcp@latest", "--usage-statistics"]

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.

Update checks

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.

Requirements

Getting started

Enable remote debugging once at brave://inspect/#remote-debugging, then add the following config to your MCP client to attach to your running Brave:

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

[!NOTE] Using brave-mcp@latest ensures that your MCP client will always use the latest version of the Brave DevTools MCP server.

Leave out --autoConnect to have the server launch its own Brave with a dedicated profile instead.

If you are interested in doing only basic browser tasks, use the --slim mode:

{
  "mcpServers": {
    "brave-devtools": {
      "command": "npx",
      "args": ["-y", "brave-mcp@latest", "--slim", "--headless"]
    }
  }
}

See Slim tool reference.

MCP Client configuration

For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our Client Configurations Guide. To attach to your running Brave, add --autoConnect to the server arguments shown there.

Your first prompt

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

Check the performance of https://brave.com

Brave asks you to allow the connection. After you click Allow, your MCP client opens the page in Brave and records a performance trace.

[!NOTE] The MCP server connects to Brave only when the MCP client first uses a tool that needs a browser, not when the client starts. Without --autoConnect, that is when the server launches its own Brave.

CLI

The package also includes the brave-devtools CLI. Use it to control the browser from your terminal without MCP:

npm i brave-mcp@latest -g
brave-devtools navigate_page 1 --url "https://brave.com"
brave-devtools take_screenshot 1 --filePath screenshot.png
brave-devtools stop

See the CLI guide for all commands and options.

Skills

The package includes skills that teach your agent how to use Brave DevTools:

| Skill | Use it to | | --------------------------------------------------------- | ---------------------------------------------- | | brave-devtools | Debug and automate pages with the MCP tools. | | brave-devtools-cli | Run the CLI and write shell scripts with it. | | a11y-debugging | Audit and fix accessibility issues. | | cookie-debugging | Debug cookies, sessions, and authentication. | | debug-optimize-lcp | Debug and improve Largest Contentful Paint. | | memory-leak-debugging | Find and fix memory leaks. | | troubleshooting | Fix connection problems between MCP and Brave. |

Install skills as a plugin

A plugin installs the MCP server and all skills, including the CLI skill:

  • Claude Code: Run /plugin marketplace add triuzzi/brave-devtools-mcp, then /plugin install brave-devtools-mcp@brave-devtools-plugins.
  • Copilot / VS Code: Run Chat: Install Plugin From Source and enter triuzzi/brave-devtools-mcp.
  • Gemini CLI: Run gemini extensions install --auto-update https://github.com/triuzzi/brave-devtools-mcp.

See the Client Configurations Guide for more information.

Install skills manually

If your agent does not support plugins, copy the skill folders into the skills directory of your agent. The npm package contains the skills:

npm i brave-mcp@latest -g
# Example for Claude Code. Use the skills directory of your agent.
mkdir -p ~/.claude/skills
cp -R "$(npm root -g)/brave-mcp/skills/brave-devtools-cli" ~/.claude/skills/

[!IMPORTANT] The brave-devtools-cli skill requires the CLI. Install the package globally before you use the skill.

Keep skills up to date

Skills describe the tools of a specific version. Update the skills each time you update the MCP server or the CLI. Outdated skills can tell your agent to use tools or parameters that changed.

  • Plugins: Use the update command of the plugin manager of your agent. The Gemini CLI command above enables automatic updates with --auto-update.
  • Manual installs: Update the package, then copy the skill folders again:
npm i brave-mcp@latest -g
mkdir -p ~/.claude/skills
cp -R "$(npm root -g)/brave-mcp/skills/brave-devtools-cli" ~/.claude/skills/

Tools

If you run into any issues, checkout our troubleshooting guide. See the full Tool reference for a complete list of all supported MCP capabilities.

Configuration

Find the complete list of server parameters (e.g., --headless, --isolated, --slim) and how to configure WebSocket connections in the Configuration Guide.

For basic browser tasks only, the --slim flag exposes a reduced set of tools. See the Slim tool reference.

Advanced usage

For advanced features such as handling concurrent sessions, persistent user data directories, connecting to a running Brave instance instead of starting a new one, or debugging on Android, see our Advanced Usage Guide.

Known limitations

See Troubleshooting.

Integrating as a browser subagent

If you are developing agentic tooling and want to provide an integrated browser subagent as part of your product, we recommend building on top of Brave DevTools for agents.

For a reference implementation, see the Gemini CLI browser agent documentation.