{"slug": "brave-devtools-mcp-control-brave-from-claude-codex-and-cursor", "title": "Brave DevTools MCP – Control Brave from Claude, Codex, and Cursor", "summary": "Brave Software released brave-mcp, a Model Context Protocol server that gives Claude Code, Codex, Cursor, OpenCode, and other MCP clients native access to Brave for browser automation, network and console debugging, performance analysis, screenshots, accessibility inspection, and memory profiling. The tool offers full parity with Chrome DevTools MCP, is currently 0 commits behind upstream, and disables usage telemetry by default, with a standalone CLI included.", "body_md": "**Full Chrome DevTools MCP parity, rebuilt for Brave.**\n\n`brave-mcp`\n\ngives 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](/triuzzi/brave-devtools-mcp/blob/main/docs/cli.md) CLI is included too.\n\n```\nclaude mcp add brave-devtools --scope user -- npx -y brave-mcp@latest\ncursor --add-mcp '{\"name\":\"brave-devtools\",\"command\":\"npx\",\"args\":[\"-y\",\"brave-mcp@latest\"]}'\ncodex mcp add brave-devtools -- npx -y brave-mcp@latest\nopencode mcp add brave-devtools -- npx -y brave-mcp@latest\n```\n\nRestart your client, then try this prompt:\n\nOpen my app in Brave. Find console errors and failed network requests, inspect the accessibility tree, run Lighthouse, and explain the highest-impact issue.\n\n| Capability | `brave-mcp` |\n`chrome-devtools-mcp` |\n|---|---|---|\n| Browser launched and discovered natively | Brave Release, Beta, and Nightly | Chrome Stable, Beta, Dev, and Canary |\n| Attach to an existing browser | Brave profiles, HTTP, or WebSocket | Chrome profiles, HTTP, or WebSocket |\n| Upstream DevTools features | Full parity; currently 0 commits behind | Source implementation |\n| Usage telemetry | Disabled by default | Enabled by default |\n| Standalone CLI | `brave-devtools` |\n`chrome-devtools` |\n\nUse [Chrome DevTools MCP](https://github.com/ChromeDevTools/chrome-devtools-mcp) when your target browser is Chrome. Use `brave-mcp`\n\nwhen your target browser is Brave and you want Brave-native discovery, profiles, channels, naming, and privacy defaults without giving up upstream features.\n\n**Get performance insights**: Uses[Chrome DevTools](https://github.com/ChromeDevTools/devtools-frontend)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](https://github.com/puppeteer/puppeteer)to automate actions in Brave and automatically wait for action results.\n\n`brave-mcp`\n\nexposes content of the browser instance to the MCP clients\nallowing them to inspect, debug, and modify any data in the browser or DevTools.\nAvoid sharing sensitive or personal information that you don't want to share with\nMCP clients.\n\n`brave-mcp`\n\nofficially supports the current Brave release. Beta and Nightly channels can be selected explicitly.\n\nPerformance tools may send trace URLs to the Google CrUX API to fetch real-user\nexperience data. This helps provide a holistic performance picture by\npresenting field data alongside lab data. This data is collected by the [Chrome\nUser Experience Report (CrUX)](https://developer.chrome.com/docs/crux). To disable\nthis, run with the `--no-performance-crux`\n\nflag.\n\nUsage statistics collection is **disabled by default** in this fork. It can be enabled explicitly with `--usage-statistics`\n\n, which uses the upstream Google Clearcut implementation:\n\n```\n\"args\": [\"-y\", \"brave-mcp@latest\", \"--usage-statistics\"]\n```\n\nWhen enabled, Google handles this data in accordance with the [Google Privacy Policy](https://policies.google.com/privacy). Collection remains disabled if `BRAVE_DEVTOOLS_MCP_NO_USAGE_STATISTICS`\n\nor `CI`\n\nis set.\n\nBy default, the server periodically checks the npm registry for updates and logs a notification when a newer version is available.\nYou can disable these update checks by setting `BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHECKS`\n\n.\n\nAdd the following config to your MCP client:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"brave-mcp@latest\"]\n    }\n  }\n}\n```\n\nNote\n\nUsing `brave-mcp@latest`\n\nensures that your MCP client will always use the latest version of the Brave DevTools MCP server.\n\nIf you are interested in doing only basic browser tasks, use the `--slim`\n\nmode:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"brave-mcp@latest\", \"--slim\", \"--headless\"]\n    }\n  }\n}\n```\n\nSee [Slim tool reference](/triuzzi/brave-devtools-mcp/blob/main/docs/slim-tool-reference.md).\n\n## Amp\n\nFollow[https://ampcode.com/manual#mcp](https://ampcode.com/manual#mcp)and use the config provided above. You can also install the Brave DevTools MCP server using the CLI:\n\n```\namp mcp add brave-devtools -- npx brave-mcp@latest\n```\n\n## Antigravity\n\nTo use the Brave DevTools MCP server follow the instructions from [Antigravity's docs](https://antigravity.google/docs/mcp) to install a custom MCP server. Add the following config to the MCP servers config:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"brave-mcp@latest\",\n        \"--browser-url=http://127.0.0.1:9222\"\n      ]\n    }\n  }\n}\n```\n\nThis 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.\n\nBrave 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.\n\n## Bob\n\nFollow the [IBM Bob MCP guide](https://bob.ibm.com/docs/ide/configuration/mcp/mcp-in-bob) and add the Brave DevTools MCP server to your Bob MCP configuration. Use the global config (`~/.bob/mcp.json`\n\n) to apply it across all workspaces, or a project config (`.bob/mcp.json`\n\n) to scope it to one project:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"brave-mcp@latest\"]\n    }\n  }\n}\n```\n\nYou 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.\n\n## Claude Code\n\n**Install via CLI (MCP only)**\n\nUse the Claude Code CLI to add the Brave DevTools MCP server ([guide](https://code.claude.com/docs/en/mcp)):\n\n```\nclaude mcp add brave-devtools --scope user npx brave-mcp@latest\n```\n\n**Install as a Plugin (MCP + Skills)**\n\n[!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.\n\nTo install Brave DevTools MCP with skills, add the marketplace registry in Claude Code:\n\n```\n/plugin marketplace add triuzzi/brave-devtools-mcp\n```\n\nThen, install the plugin:\n\n```\n/plugin install brave-devtools-mcp@brave-devtools-plugins\n```\n\nRestart Claude Code to have the MCP server and skills load (check with `/skills`\n\n).\n\n[!TIP] If the plugin installation fails with a\n\n`Failed to clone repository`\n\nerror (e.g., HTTPS connectivity issues behind a corporate firewall), see the[troubleshooting guide]for workarounds, or use the CLI installation method above instead.\n\n## Cline\n\nFollow[https://docs.cline.bot/mcp/configuring-mcp-servers](https://docs.cline.bot/mcp/configuring-mcp-servers)and use the config provided above.\n\n## Codex\n\nFollow the[configure MCP guide](https://developers.openai.com/codex/mcp/#configure-with-the-cli)using the standard config from above. You can also install the Brave DevTools MCP server using the Codex CLI:\n\n```\ncodex mcp add brave-devtools -- npx brave-mcp@latest\n```\n\n**On Windows 11**\n\nConfigure the Brave install location and increase the startup timeout by updating `.codex/config.toml`\n\nand adding the following `env`\n\nand `startup_timeout_ms`\n\nparameters:\n\n```\n[mcp_servers.brave-devtools]\ncommand = \"cmd\"\nargs = [\n    \"/c\",\n    \"npx\",\n    \"-y\",\n    \"brave-mcp@latest\",\n]\nenv = { SystemRoot=\"C:\\\\Windows\", PROGRAMFILES=\"C:\\\\Program Files\" }\nstartup_timeout_ms = 20_000\n```\n\n## Copilot CLI\n\nStart Copilot CLI:\n\n```\ncopilot\n```\n\nStart the dialog to add a new MCP server by running:\n\n```\n/mcp add\n```\n\nConfigure the following fields and press `CTRL+S`\n\nto save the configuration:\n\n**Server name:**`brave-devtools`\n\n**Server Type:**`[1] Local`\n\n**Command:**`npx -y brave-mcp@latest`\n\n## Copilot / VS Code\n\n**Install as a Plugin (Recommended)**\n\nThe easiest way to get up and running is to install `brave-mcp`\n\nas an agent plugin.\nThis bundles the **MCP server** and all **skills** together, so your agent gets both the tools\nand the expert guidance it needs to use them effectively.\n\n- Open the\n**Command Palette**(`Cmd+Shift+P`\n\non macOS or`Ctrl+Shift+P`\n\non Windows/Linux). - Search for and run the\n**Chat: Install Plugin From Source** command. - Paste in our repository name:\n`triuzzi/brave-devtools-mcp`\n\n.\n\nThat's it! Your agent is now supercharged with Brave DevTools capabilities.\n\n**Install as an MCP Server (MCP only)**\n\n**Click the button to install:**\n\n**Or install manually:**\n\nFollow the VS Code [MCP configuration guide](https://code.visualstudio.com/docs/copilot/chat/mcp-servers#_add-an-mcp-server) using the standard config from above, or use the CLI:\n\nFor macOS and Linux:\n\n```\ncode --add-mcp '{\"name\":\"io.github.triuzzi/brave-devtools-mcp\",\"command\":\"npx\",\"args\":[\"-y\",\"brave-mcp\"],\"env\":{}}'\n```\n\nFor Windows (PowerShell):\n\n```\ncode --add-mcp '{\"\"\"name\"\"\":\"\"\"io.github.triuzzi/brave-devtools-mcp\"\"\",\"\"\"command\"\"\":\"\"\"npx\"\"\",\"\"\"args\"\"\":[\"\"\"-y\"\"\",\"\"\"brave-mcp\"\"\"]}'\n```\n\n## Cursor\n\n**Click the button to install:**\n\n**Or install manually:**\n\nGo to `Cursor Settings`\n\n-> `MCP`\n\n-> `New MCP Server`\n\n. Use the config provided above.\n\n## Devin CLI\n\n**Install via CLI (MCP only)**\n\nUse the Devin CLI to add the Brave DevTools MCP server ([guide](https://docs.devin.ai/cli/extensibility/mcp/configuration)):\n\n```\ndevin mcp add brave-devtools -- npx brave-mcp@latest\n```\n\n## Gemini CLI\n\nInstall the Brave DevTools MCP server using the Gemini CLI.**Project wide:**\n\n```\n# Either MCP only:\ngemini mcp add brave-devtools npx brave-mcp@latest\n# Or as a Gemini extension (MCP+Skills):\ngemini extensions install --auto-update https://github.com/triuzzi/brave-devtools-mcp\n```\n\n**Globally:**\n\n```\ngemini mcp add -s user brave-devtools npx brave-mcp@latest\n```\n\nAlternatively, follow the [MCP guide](https://github.com/google-gemini/gemini-cli/blob/main/docs/tools/mcp-server.md#how-to-set-up-your-mcp-server) and use the standard config from above.\n\n## Gemini Code Assist\n\nFollow the[configure MCP guide](https://cloud.google.com/gemini/docs/codeassist/use-agentic-chat-pair-programmer#configure-mcp-servers)using the standard config from above.\n\n## JetBrains AI Assistant & Junie\n\nGo to `Settings | Tools | AI Assistant | Model Context Protocol (MCP)`\n\n-> `Add`\n\n. Use the config provided above.\nThe same way brave-mcp can be configured for JetBrains Junie in `Settings | Tools | Junie | MCP Settings`\n\n-> `Add`\n\n. Use the config provided above.\n\n## Kiro\n\nIn **Kiro Settings**, go to `Configure MCP`\n\n> `Open Workspace or User MCP Config`\n\n> Use the configuration snippet provided above.\n\nOr, from the IDE **Activity Bar** > `Kiro`\n\n> `MCP Servers`\n\n> `Click Open MCP Config`\n\n. Use the configuration snippet provided above.\n\n## Katalon Studio\n\nThe Brave DevTools MCP server can be used with Katalon StudioAssist via an MCP proxy.\n\n**Step 1:** Install the MCP proxy by following the [MCP proxy setup guide](https://docs.katalon.com/katalon-studio/studioassist/mcp-servers/setting-up-mcp-proxy-for-stdio-mcp-servers).\n\n**Step 2:** Start the Brave DevTools MCP server with the proxy:\n\n```\nmcp-proxy --transport streamablehttp --port 8080 -- npx -y brave-mcp@latest\n```\n\n**Note:** You may need to pick another port if 8080 is already in use.\n\n**Step 3:** In Katalon Studio, add the server to StudioAssist with the following settings:\n\n**Connection URL:**`http://127.0.0.1:8080/mcp`\n\n**Transport type:**`HTTP`\n\nOnce connected, the Brave DevTools MCP tools will be available in StudioAssist.\n\n## Mistral Vibe\n\nAdd in ~/.vibe/config.toml:\n\n```\n[[mcp_servers]]\nname = \"brave-devtools\"\ntransport = \"stdio\"\ncommand = \"npx\"\nargs = [\"brave-mcp@latest\"]\n```\n\n## OpenCode\n\nAdd the following configuration to your `opencode.json`\n\nfile. If you don't have one, create it at `~/.config/opencode/opencode.json`\n\n([guide](https://opencode.ai/docs/mcp-servers)):\n\n```\n{\n  \"$schema\": \"https://opencode.ai/config.json\",\n  \"mcp\": {\n    \"brave-devtools\": {\n      \"type\": \"local\",\n      \"command\": [\"npx\", \"-y\", \"brave-mcp@latest\"]\n    }\n  }\n}\n```\n\n## Qoder\n\nIn **Qoder Settings**, go to `MCP Server`\n\n> `+ Add`\n\n> Use the configuration snippet provided above.\n\nAlternatively, follow the [MCP guide](https://docs.qoder.com/user-guide/chat/model-context-protocol) and use the standard config from above.\n\n## Qoder CLI\n\nInstall the Brave DevTools MCP server using the Qoder CLI ([guide](https://docs.qoder.com/cli/using-cli#mcp-servers)):\n\n**Project wide:**\n\n```\nqodercli mcp add brave-devtools -- npx brave-mcp@latest\n```\n\n**Globally:**\n\n```\nqodercli mcp add -s user brave-devtools -- npx brave-mcp@latest\n```\n\n## Warp\n\nGo to `Settings | AI | Manage MCP Servers`\n\n-> `+ Add`\n\nto [add an MCP Server](https://docs.warp.dev/knowledge-and-collaboration/mcp#adding-an-mcp-server). Use the config provided above.\n\n## Windsurf\n\nFollow the[configure MCP guide](https://docs.windsurf.com/windsurf/cascade/mcp#mcp-config-json)using the standard config from above.\n\nEnter the following prompt in your MCP Client to check if everything is working:\n\n```\nCheck the performance of https://developers.chrome.com\n```\n\nYour MCP client should open the browser and record a performance trace.\n\nNote\n\nThe MCP server will start the browser automatically once the MCP client uses a tool that requires a running browser instance. Connecting to the Brave DevTools MCP server on its own will not automatically start the browser.\n\nIf you run into any issues, checkout our [troubleshooting guide](/triuzzi/brave-devtools-mcp/blob/main/docs/troubleshooting.md).\n\n**Input automation**(10 tools)** Navigation automation**(6 tools)** Emulation**(2 tools)** Performance**(3 tools)** Network**(2 tools)** Debugging**(8 tools)** Memory**(12 tools)`take_heapsnapshot`\n\n`close_heapsnapshot`\n\n`compare_heapsnapshots`\n\n`get_heapsnapshot_class_nodes`\n\n`get_heapsnapshot_details`\n\n`get_heapsnapshot_dominators`\n\n`get_heapsnapshot_duplicate_strings`\n\n`get_heapsnapshot_edges`\n\n`get_heapsnapshot_object_details`\n\n`get_heapsnapshot_retainers`\n\n`get_heapsnapshot_retaining_paths`\n\n`get_heapsnapshot_summary`\n\n**Extensions**(5 tools)** Third-party**(2 tools)** WebMCP**(2 tools)** Progressive Web Apps**(4 tools)\n\nThe Brave DevTools MCP server supports the following configuration option:\n\n-\nIf specified, automatically connects to a Brave instance running locally from the user data directory identified by the channel parameter (default channel is release). Requires remote debugging to be enabled via brave://inspect/#remote-debugging.`--autoConnect`\n\n/`--auto-connect`\n\n**Type:** boolean**Default:**`false`\n\n-\nConnect to a running, debuggable Brave instance (e.g.`--browserUrl`\n\n/`--browser-url`\n\n,`-u`\n\n`http://127.0.0.1:9222`\n\n). For more details see:[https://github.com/triuzzi/brave-devtools-mcp#connecting-to-a-running-brave-instance](https://github.com/triuzzi/brave-devtools-mcp#connecting-to-a-running-brave-instance).**Type:** string**Default:**`false`\n\n-\nWebSocket endpoint to connect to a running Brave instance (e.g., ws://127.0.0.1:9222/devtools/browser/). Alternative to --browserUrl.`--wsEndpoint`\n\n/`--ws-endpoint`\n\n,`-w`\n\n**Type:** string**Default:**`false`\n\n-\nCustom headers for WebSocket connection in JSON format (e.g., '{\"Authorization\":\"Bearer token\"}'). Only works with --wsEndpoint.`--wsHeaders`\n\n/`--ws-headers`\n\n**Type:** string**Default:**`false`\n\n-\nWhether to run in headless (no UI) mode.`--headless`\n\n**Type:** boolean**Default:**`false`\n\n-\nPath to a custom Brave executable. Can also be set via BRAVE_PATH.`--executablePath`\n\n/`--executable-path`\n\n,`-e`\n\n**Type:** string**Default:**`false`\n\n-\nIf specified, creates a temporary user-data-dir that is automatically cleaned up after the browser is closed. Defaults to false.`--isolated`\n\n**Type:** boolean**Default:**`false`\n\n-\nPath to the user data directory for Brave. Default is $HOME/.cache/brave-devtools-mcp/brave-profile$CHANNEL_SUFFIX_IF_NON_RELEASE`--userDataDir`\n\n/`--user-data-dir`\n\n**Type:** string**Default:**`false`\n\n-\nSpecify a different Brave channel. The default is the release channel.`--channel`\n\n**Type:** string**Choices:**`release`\n\n,`beta`\n\n,`nightly`\n\n**Default:**`false`\n\n-\nPath to a file to write debug logs to. Set the env variable`--logFile`\n\n/`--log-file`\n\n`DEBUG`\n\nto`*`\n\nto enable verbose logs. Useful for submitting bug reports.**Type:** string**Default:**`false`\n\n-\nInitial viewport size for Brave instances started by the server. For example,`--viewport`\n\n`1280x720`\n\n. In headless mode, max size is 3840x2160px.**Type:** string**Default:**`false`\n\n-\nProxy server configuration for Brave passed as --proxy-server when launching the browser. See`--proxyServer`\n\n/`--proxy-server`\n\n[https://www.chromium.org/developers/design-documents/network-settings/](https://www.chromium.org/developers/design-documents/network-settings/)for details.**Type:** string**Default:**`false`\n\n-\nIf enabled, ignores errors relative to self-signed and expired certificates. Use with caution.`--acceptInsecureCerts`\n\n/`--accept-insecure-certs`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to expose pageId on page-scoped tools and route requests by page ID (useful for concurrent agent sessions).`--experimentalPageIdRouting`\n\n/`--experimental-page-id-routing`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to enable automation over DevTools targets`--experimentalDevtools`\n\n/`--experimental-devtools`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to enable coordinate-based tools such as click_at(x,y). Usually requires a computer-use model able to produce accurate coordinates by looking at screenshots.`--experimentalVision`\n\n/`--experimental-vision`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to enable memory debugging tools.`--memoryDebugging`\n\n/`--memory-debugging`\n\n,`-experimentalMemory`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to output structured formatted content.`--experimentalStructuredContent`\n\n/`--experimental-structured-content`\n\n**Type:** boolean**Default:**`false`\n\n-\nWhether to include all kinds of pages such as webviews or background pages as pages.`--experimentalIncludeAllPages`\n\n/`--experimental-include-all-pages`\n\n**Type:** boolean**Default:**`false`\n\n-\nExposes experimental screencast tools (requires ffmpeg). Install ffmpeg`--experimentalScreencast`\n\n/`--experimental-screencast`\n\n[https://www.ffmpeg.org/download.html](https://www.ffmpeg.org/download.html)and ensure it is available in the MCP server PATH.**Type:** boolean**Default:**`false`\n\n-\nPath to ffmpeg executable for screencast recording.`--experimentalFfmpegPath`\n\n/`--experimental-ffmpeg-path`\n\n**Type:** string**Default:**`false`\n\n-\nSet to true to enable debugging WebMCP tools. Requires a recent Brave version with the following flags:`--categoryExperimentalWebmcp`\n\n/`--category-experimental-webmcp`\n\n`--enable-features=WebMCP,DevToolsWebMCPSupport`\n\n**Type:** boolean**Default:**`false`\n\n-\nAdditional arguments for Brave. Only applies when Brave is launched by brave-devtools-mcp.`--braveArg`\n\n/`--brave-arg`\n\n**Type:** array**Default:**`false`\n\n-\nRestricts browser's network access by blocking specified URL patterns (uses`--blockedUrlPattern`\n\n/`--blocked-url-pattern`\n\n[https://urlpattern.spec.whatwg.org/](https://urlpattern.spec.whatwg.org/)). Silently detaches from targets with blocked URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns.**Type:** array**Default:**`false`\n\n-\nRestricts browser's network access by allowing only specified URL patterns (uses`--allowedUrlPattern`\n\n/`--allowed-url-pattern`\n\n[https://urlpattern.spec.whatwg.org/](https://urlpattern.spec.whatwg.org/)). Requires a recent Brave version. Silently detaches from targets with unallowed URLs upon connection, and blocks runtime requests (including navigations and subresources). Accepts an array of patterns.**Type:** array**Default:**`false`\n\n-\nExplicitly disable default arguments for Brave. Only applies when Brave is launched by brave-devtools-mcp.`--ignoreDefaultBraveArg`\n\n/`--ignore-default-brave-arg`\n\n**Type:** array**Default:**`false`\n\n-\nSet to false to exclude tools related to emulation.`--categoryEmulation`\n\n/`--category-emulation`\n\n**Type:** boolean**Default:**`true`\n\n-\nSet to false to exclude tools related to performance.`--categoryPerformance`\n\n/`--category-performance`\n\n**Type:** boolean**Default:**`true`\n\n-\nSet to false to exclude tools related to network.`--categoryNetwork`\n\n/`--category-network`\n\n**Type:** boolean**Default:**`true`\n\n-\nSet to true to include tools related to extensions. This feature is only supported with a pipe connection; autoConnect, browserUrl, and wsEndpoint are not supported.`--categoryExtensions`\n\n/`--category-extensions`\n\n**Type:** boolean**Default:**`false`\n\n-\nSet to true to enable third-party developer tools exposed by the inspected page itself`--categoryExperimentalThirdParty`\n\n/`--category-experimental-third-party`\n\n**Type:** boolean**Default:**`false`\n\n-\nSet to true to include tools for automating Progressive Web Apps (install, launch, uninstall, and OS state). This feature is only supported with a pipe connection; autoConnect, browserUrl, and wsEndpoint are not supported.`--categoryPwa`\n\n/`--category-pwa`\n\n**Type:** boolean**Default:**`false`\n\n-\nSet to false to disable sending URLs from performance traces to CrUX API to get field performance data.`--performanceCrux`\n\n/`--performance-crux`\n\n**Type:** boolean**Default:**`true`\n\n-\nUsage statistics collection is disabled by default in this fork.`--usageStatistics`\n\n/`--usage-statistics`\n\n**Type:** boolean**Default:**`false`\n\n-\nOverride the default output format used by take_screenshot when the caller does not specify one. JPEG and WebP are ~3-5x smaller than PNG, which helps reduce context size in AI conversations. Unset preserves the existing default (\"png\").`--screenshotFormat`\n\n/`--screenshot-format`\n\n**Type:** string**Choices:**`jpeg`\n\n,`png`\n\n,`webp`\n\n**Default:**`false`\n\n-\nOverride the default compression quality (0-100) used by take_screenshot for JPEG and WebP when the caller does not specify one. Lower values mean smaller files. Ignored for PNG. Unset preserves the Puppeteer default.`--screenshotQuality`\n\n/`--screenshot-quality`\n\n**Type:** number**Default:**`false`\n\n-\nMaximum width in pixels for screenshots. If the captured image is wider, it is downscaled (preserving aspect ratio) before being returned. Reduces context size in AI conversations. Unset means no resize.`--screenshotMaxWidth`\n\n/`--screenshot-max-width`\n\n**Type:** number**Default:**`false`\n\n-\nMaximum height in pixels for screenshots. If the captured image is taller, it is downscaled (preserving aspect ratio) before being returned. Can be combined with --screenshot-max-width; the smaller scale factor wins. Unset means no resize.`--screenshotMaxHeight`\n\n/`--screenshot-max-height`\n\n**Type:** number**Default:**`false`\n\n-\nExposes a \"slim\" set of 3 tools covering navigation, script execution and screenshots only. Useful for basic browser tasks.`--slim`\n\n**Type:** boolean**Default:**`false`\n\n-\nIf true, redacts some of the network headers considered sensitive before returning to the client.`--redactNetworkHeaders`\n\n/`--redact-network-headers`\n\n**Type:** boolean**Default:**`false`\n\n-\nIf set, disables the default path restriction that applies when the MCP client does not negotiate the roots capability. By default, file-writing tools are restricted to the OS temp directory when no roots are configured. Use this only when connecting a trusted local client that does not implement MCP roots and requires access to paths outside the temp directory.`--allowUnrestrictedPaths`\n\n/`--allow-unrestricted-paths`\n\n**Type:** boolean**Default:**`false`\n\nPass them via the `args`\n\nproperty in the JSON configuration. For example:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"brave-mcp@latest\",\n        \"--channel=nightly\",\n        \"--headless=true\",\n        \"--isolated=true\"\n      ]\n    }\n  }\n}\n```\n\nYou can connect directly to a Brave WebSocket endpoint and include custom headers (e.g., for authentication):\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"brave-mcp@latest\",\n        \"--wsEndpoint=ws://127.0.0.1:9222/devtools/browser/<id>\",\n        \"--wsHeaders={\\\"Authorization\\\":\\\"Bearer YOUR_TOKEN\\\"}\"\n      ]\n    }\n  }\n}\n```\n\nTo get the WebSocket endpoint from a running Brave instance, visit `http://127.0.0.1:9222/json/version`\n\nand look for the `webSocketDebuggerUrl`\n\nfield.\n\nYou can also run `npx brave-mcp@latest --help`\n\nto see all available configuration options.\n\nMost MCP clients start one Brave DevTools MCP server per conversation. If your\nclient shares a single server instance across concurrent agents or subagents,\nstart the server with `--experimentalPageIdRouting`\n\n. This exposes `pageId`\n\non\npage-scoped tools so each agent can route tool calls to the tab it is working\nwith.\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"brave-mcp@latest\", \"--experimentalPageIdRouting\"]\n    }\n  }\n}\n```\n\nIf you run multiple independent MCP client sessions and want each session to\nlaunch its own temporary Brave profile, also pass `--isolated`\n\n. This avoids\nsharing the default Brave DevTools MCP user data directory between those\nserver instances.\n\nBy default, `brave-mcp`\n\nstarts the Brave release channel using the following user\ndata directory:\n\n- Linux / macOS:\n`$HOME/.cache/brave-devtools-mcp/brave-profile`\n\n- Windows:\n`%USERPROFILE%\\.cache\\brave-devtools-mcp\\brave-profile`\n\nFor non-release channels, the channel name is appended to the directory name, for example\n`brave-profile-nightly`\n\n.\n\nThe user data directory is not cleared between runs and is reused for subsequent\nruns with the same channel. Only one browser can use it at a time. Set the `isolated`\n\noption to `true`\n\nto use a temporary user data directory instead which will be cleared\nautomatically after the browser is closed.\n\nBy default, the Brave DevTools MCP server will start a new Brave instance with a dedicated profile. This might not be ideal in all situations:\n\n- If you would like to maintain the same application state when alternating between manual site testing and agent-driven testing.\n- When the MCP needs to sign into a website. Some accounts may prevent sign-in when the browser is controlled via WebDriver (the default launch mechanism for the Brave DevTools MCP server).\n- If you're running your LLM inside a sandboxed environment, but you would like to connect to a Brave instance that runs outside the sandbox.\n\nIn these cases, start Brave first and let the Brave DevTools MCP server connect to it. There are two ways to do so:\n\n**Automatic connection**: best for sharing state between manual and agent-driven testing.** Manual connection via remote debugging port**: best when running inside a sandboxed environment.\n\n**Step 1:** Set up remote debugging in Brave\n\nIn Brave, do the following to set up remote debugging:\n\n- Navigate to\n`brave://inspect/#remote-debugging`\n\nto enable remote debugging. - Follow the dialog UI to allow or disallow incoming debugging connections.\n\n**Step 2:** Configure Brave DevTools MCP server to automatically connect to a running Brave instance\n\nTo connect the `brave-mcp`\n\nserver to the running Brave instance, use\n`--autoConnect`\n\ncommand line argument for the MCP server.\n\nThe following code snippet is an example configuration for gemini-cli:\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"brave-mcp@latest\", \"--autoConnect\"]\n    }\n  }\n}\n```\n\n**Step 3:** Test your setup\n\nMake sure your browser is running. Open gemini-cli and run the following prompt:\n\n```\nCheck the performance of https://developers.chrome.com\n```\n\nNote\n\nThe `autoConnect`\n\noption requires the user to start Brave. If the user has multiple active profiles, the MCP server connects to Brave's default profile and can access all open windows for that profile.\n\nThe Brave DevTools MCP server will try to connect to your running Brave instance. It shows a dialog asking for user permission.\n\nClicking **Allow** results in the Brave DevTools MCP server opening\n[developers.chrome.com](http://developers.chrome.com) and taking a performance\ntrace.\n\nYou can connect to a running Brave instance by using the `--browser-url`\n\noption. This is useful if you are running the MCP server in a sandboxed environment that does not allow starting a new Brave instance.\n\nHere is a step-by-step guide on how to connect to a running Brave instance:\n\n**Step 1: Configure the MCP client**\n\nAdd the `--browser-url`\n\noption to your MCP client configuration. The value of this option should be the URL of the running Brave instance. `http://127.0.0.1:9222`\n\nis a common default.\n\n```\n{\n  \"mcpServers\": {\n    \"brave-devtools\": {\n      \"command\": \"npx\",\n      \"args\": [\"brave-mcp@latest\", \"--browser-url=http://127.0.0.1:9222\"]\n    }\n  }\n}\n```\n\n**Step 2: Start the Brave browser**\n\nWarning\n\nEnabling the remote debugging port opens up a debugging port on the running browser instance. Any application on your machine can connect to this port and control the browser. Make sure that you are not browsing any sensitive websites while the debugging port is open.\n\nStart the Brave browser with the remote debugging port enabled. Make sure to close any running Brave instances before starting a new one with the debugging port enabled. The port number you choose must be the same as the one you specified in the `--browser-url`\n\noption in your MCP client configuration.\n\nUse a dedicated user data directory when enabling the remote debugging port so your regular browsing profile and data are not exposed to the debugging session.\n\n**macOS**\n\n```\n/Applications/Brave\\ Browser.app/Contents/MacOS/Brave\\ Browser --remote-debugging-port=9222 --user-data-dir=/tmp/brave-profile-release\n```\n\n**Linux**\n\n```\n/usr/bin/brave-browser --remote-debugging-port=9222 --user-data-dir=/tmp/brave-profile-release\n```\n\n**Windows**\n\n```\n\"C:\\Program Files\\BraveSoftware\\Brave-Browser\\Application\\brave.exe\" --remote-debugging-port=9222 --user-data-dir=\"%TEMP%\\brave-profile-release\"\n```\n\n**Step 3: Test your setup**\n\nAfter configuring the MCP client and starting the Brave browser, you can test your setup by running a simple prompt in your MCP client:\n\n```\nCheck the performance of https://developers.chrome.com\n```\n\nYour MCP client should connect to the running Brave instance and receive a performance report.\n\nIf you hit VM-to-host port forwarding issues, see the “Remote debugging between virtual machine (VM) and host fails” section in [ docs/troubleshooting.md](/triuzzi/brave-devtools-mcp/blob/main/docs/troubleshooting.md#remote-debugging-between-virtual-machine-vm-and-host-fails).\n\nFor more details on remote debugging, see the [Chromium DevTools documentation](https://developer.chrome.com/docs/devtools/remote-debugging/).\n\nPlease consult [these instructions](/triuzzi/brave-devtools-mcp/blob/main/docs/debugging-android.md).\n\nSee [Troubleshooting](/triuzzi/brave-devtools-mcp/blob/main/docs/troubleshooting.md).\n\nIf 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.\n\nFor a reference implementation, see the [Gemini CLI browser agent documentation](https://geminicli.com/docs/core/subagents/#browser-agent).", "url": "https://wpnews.pro/news/brave-devtools-mcp-control-brave-from-claude-codex-and-cursor", "canonical_source": "https://github.com/triuzzi/brave-devtools-mcp", "published_at": "2026-08-12 07:33:08+00:00", "updated_at": "2026-08-12 07:40:42.569178+00:00", "lang": "en", "topics": ["developer-tools", "ai-tools", "ai-agents"], "entities": ["Brave Software", "Claude Code", "Codex", "Cursor", "OpenCode", "Chrome DevTools MCP", "puppeteer", "Google CrUX API"], "alternates": {"html": "https://wpnews.pro/news/brave-devtools-mcp-control-brave-from-claude-codex-and-cursor", "markdown": "https://wpnews.pro/news/brave-devtools-mcp-control-brave-from-claude-codex-and-cursor.md", "text": "https://wpnews.pro/news/brave-devtools-mcp-control-brave-from-claude-codex-and-cursor.txt", "jsonld": "https://wpnews.pro/news/brave-devtools-mcp-control-brave-from-claude-codex-and-cursor.jsonld"}}