v1.11.0

What's Changed

• feat: sync Brave with Chrome DevTools 1.11.0 by @triuzzi in #37

Full Changelog: v1.10.1...v1.11.0

v1.10.1

What's Changed

• docs: recommend --autoConnect in README setup by @triuzzi in #33
• feat: sync Brave with Chrome DevTools 1.10.1 by @triuzzi in #34

Full Changelog: v1.9.0...v1.10.1

v1.9.0

What's Changed

• fix(ci): stop the MCP registry publish from firing on tag push by @triuzzi in #29
• feat: sync Brave with Chrome DevTools 1.9.0 by @triuzzi in #31
• chore: restore Chrome DevTools upstream ancestry by @triuzzi in #32

Full Changelog: v1.8.0...v1.9.0

v1.8.0

Syncs the Brave fork with Chrome DevTools MCP 1.8.0 plus the commits that landed on upstream main after that release. The fork is now 0 commits behind ChromeDevTools/chrome-devtools-mcp:main.

Upstream changes

• pageId is required on page-scoped tools by default — pageIdRouting replaces --experimentalPageIdRouting; pass --no-page-id-routing to keep targeting the selected page
• new query_heapsnapshot tool; get_heapsnapshot_summary reports memory kept alive by contexts; get_heapsnapshot_edges takes additional params
• sizes are reported as human-readable ranges
• --allow-unrestricted-paths defaults to true for the CLI; default performance trace buffer is 1.2gb
• unknown CLI args and unknown MCP server options are now rejected/warned
• CLI/MCP option definitions moved from src/bin/*-cli-options.ts to src/config/{cli,mcp}-options.ts, and the devtools-frontend submodule moved to third_party/devtools-frontend

Brave adaptations

Brave branding, executable and channel handling, brave-mcp package/script names, usage statistics off by default, --brave-arg / --ignore-default-brave-arg, the BRAVE_DEVTOOLS_MCP_* environment variables, and spawn-only flags stripped from daemon args in attach mode.

Full Changelog: v1.7.1...v1.8.0

v1.7.1

What's Changed

• fix: stabilize PWA launch and sharpen project page by @triuzzi in #24
• fix: honor configured navigation timeout by @triuzzi in #25
• chore: release brave-mcp 1.7.1 by @triuzzi in #26
• chore: restore Chrome DevTools upstream ancestry by @triuzzi in #27

Full Changelog: v1.7.0...v1.7.1

v1.7.0

Full Chrome DevTools MCP parity, rebuilt for Brave.

Version 1.7.0 brings brave-mcp onto the current Chrome DevTools MCP codebase while preserving Brave-native browser discovery, profiles, channels, naming, and privacy defaults.

Why upgrade

• Use the complete upstream DevTools feature set from Brave.
• Launch Brave Release, Beta, or Nightly without hard-coded executable paths.
• Attach Claude Code, Codex, Cursor, OpenCode, or another MCP client to an existing Brave session over HTTP or WebSocket.
• Keep usage telemetry disabled by default.
• Install from npm with signed provenance, or discover the server through the official MCP Registry.

New capabilities

• Progressive Web App installation, launch, OS-state inspection, and uninstall tools.
• Multi-file uploads through upload_file.
• Optional source-mapped stack traces in console output.
• Explicit control over stable-DOM waiting in evaluate_script.
• Expanded heap-snapshot object, edge, context, and retained-size analysis.
• More reliable daemon lifecycle, screenshots, performance traces, dialogs, and network retention.

One-minute demo

Install for Claude Code:

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

Then ask:

Open my app in Brave. Find console errors and failed network requests, inspect the accessibility tree, run Lighthouse, and explain the highest-impact issue.

The same server works with Cursor, Codex, OpenCode, and any standard MCP client. See the README for one-command installation.

Verified

• Brave test matrix on Linux, macOS, and Windows.
• Node.js 22, 24, and 26.
• Memory-leak, generated-documentation, formatting, package-content, and MCP metadata gates.
• Live attach-mode verification against a real Brave instance.

Links

• npm package
• MCP Registry entry
• Pull request #23
• Full changelog

v1.6.0

Sync of the Brave fork with upstream chrome-devtools-mcp v1.6.0.

📦 npm: https://www.npmjs.com/package/brave-mcp/v/1.6.0  ·  npx brave-mcp@1.6.0

Highlights (from upstream 1.6.0)

• feat: --allow-unrestricted-paths configuration
• feat: experimentalGcfFormat flag for GCF-encoded tool responses
• feat: heap-snapshot aggregate filtering + object counts/sizes in get_heapsnapshot_details
• feat: update Lighthouse to 13.4.0
• perf: concurrent I/O in root-path resolution
• fix: selected-page fallback correctness, telemetry enum resolution, press_key modifier release, pagination of page 0
• revert: experimental navigate-allowlist (removed upstream)
• refactor: large file move/rename, per-page collectors, DevTools universe → McpPage

36 upstream commits cherry-picked on top of the Brave adaptations; 818 tests pass.

Full delta: chrome-devtools-mcp-v1.5.0…v1.6.0

v0.5.0 - CI green, Brave installed in CI

First release with fully green CI across the matrix (ubuntu/macos/windows × node 20/22/23/24).

CI fixes

• Install Brave Browser in CI before running e2e tests (run-tests.yml). The chrome-devtools test suite spawns a real Brave binary — runners come with Chrome pre-installed but not Brave, so every list_pages / take_screenshot test was failing with "Could not find Brave Browser". Adds OS-specific install steps:
  • Ubuntu: apt repo
  • macOS: brew install --cask brave-browser
  • Windows: choco install brave -y --no-progress
• Fix the lint blocker on tests/e2e/brave-integration.test.mjs: include the file in allowDefaultProject (so the TS project service can parse it), rename two unused identifiers (label, submitUid) to underscore-prefixed, and auto-format.
• Fix npm run gen to stop emitting a stale chrome-named file: scripts/generate-cli.ts now writes to brave-devtools-cli-options.ts and uses BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS in the spawn env.
• Remove .github/workflows/release-please.yml: it referenced BROWSER_AUTOMATION_BOT_TOKEN, an upstream-only secret. Releases on this fork are cut manually.

Install

npm install brave-mcp@0.5.0

v0.4.0 - chrome-devtools-mcp v0.24.0 sync

Syncs the Brave fork with upstream chrome-devtools-mcp v0.24.0.

Notable upstream changes pulled in

• feat: support third-party developer tools (upstream ChromeDevTools#1982)
• feat: agentic browsing in lighthouse (upstream ChromeDevTools#1931)
• feat(cli): generate commands for conditional tools (upstream ChromeDevTools#1962)
• fix: handle errors due to open dialogs during tool calls (upstream ChromeDevTools#1953, ChromeDevTools#1978, ChromeDevTools#1977)
• fix(input): stop native select option clicks from timing out (upstream ChromeDevTools#1960)
• fix: make sure env variables are consistently applied when parsing args (upstream ChromeDevTools#1994)
• build: fix npm start (upstream ChromeDevTools#1980) — kept pointing at brave-devtools-mcp.js
• chrome-devtools-mcp v0.24.0 release commit (upstream ChromeDevTools#1944)

Dependency updates

• chrome-devtools-frontend → 1.0.1625079
• lighthouse → 13.2.0
• puppeteer → 24.43.0
• @paulirish/trace_engine → 0.0.64
• tiktoken removed

Brave-specific adaptations

• Adapted upstream env-var refactor to use BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS (CI / opt-out env var) consistent with the existing BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS and BRAVE_DEVTOOLS_MCP_CRASH_ON_UNCAUGHT Brave env vars.
• Renamed stale chrome-devtools-mcp-cli-options imports and CHROME_DEVTOOLS_MCP_* env-var references in newly-merged test files.

Install

npm install brave-mcp@0.4.0

0.2.1

What's changed

• Sync with upstream `ChromeDevTools/chrome-devtools-mcp` (10 commits including memory snapshot info, PerformanceIssue event fix, Network redirect fix, local-build update-notification fix, etc.)
• Rebrand `docs/cli.md` for Brave (missed in the initial port)
• Fix `src/version.ts` drift (was stuck at 0.1.0) so the CLI reports the correct version and stops falsely nagging about updates

PR: #7