brave-mcp 1.9.0 → 1.10.1

package/README.md

@@ -6,7 +6,7 @@
 [![npm](https://img.shields.io/npm/v/brave-mcp.svg?logo=npm)](https://www.npmjs.com/package/brave-mcp)
 [![npm downloads](https://img.shields.io/npm/dm/brave-mcp.svg?logo=npm)](https://www.npmjs.com/package/brave-mcp)
 [![MCP Registry](https://img.shields.io/badge/MCP%20Registry-active-5B5BD6)](https://registry.modelcontextprotocol.io/v0.1/servers?search=io.github.triuzzi%2Fbrave-mcp)
-[![npm provenance](https://img.shields.io/badge/npm-provenance-2E7D32)](https://registry.npmjs.org/-/npm/v1/attestations/brave-mcp@1.7.1)
+[![npm provenance](https://img.shields.io/badge/npm-provenance-2E7D32)](https://www.npmjs.com/package/brave-mcp#provenance)
 [![upstream](https://img.shields.io/badge/upstream-0%20commits%20behind-brightgreen)](https://github.com/triuzzi/brave-devtools-mcp/compare/ChromeDevTools:main...main)
 [![license](https://img.shields.io/github/license/triuzzi/brave-devtools-mcp)](./LICENSE)
 
@@ -16,34 +16,40 @@
 
 ## 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
 
 ```bash
-claude mcp add brave-devtools --scope user -- npx -y brave-mcp@latest
+claude mcp add brave-devtools --scope user -- npx -y brave-mcp@latest --autoConnect
 ```
 
 ### Cursor
 
 ```bash
-cursor --add-mcp '{"name":"brave-devtools","command":"npx","args":["-y","brave-mcp@latest"]}'
+cursor --add-mcp '{"name":"brave-devtools","command":"npx","args":["-y","brave-mcp@latest","--autoConnect"]}'
 ```
 
 ### Codex
 
 ```bash
-codex mcp add brave-devtools -- npx -y brave-mcp@latest
+codex mcp add brave-devtools -- npx -y brave-mcp@latest --autoConnect
 ```
 
 ### OpenCode
 
 ```bash
-opencode mcp add brave-devtools -- npx -y brave-mcp@latest
+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`                |
@@ -107,14 +113,14 @@ You can disable these update checks by setting `BRAVE_DEVTOOLS_MCP_NO_UPDATE_CHE
 
 ## Getting started
 
-Add the following config to your MCP client:
+Enable remote debugging once at `brave://inspect/#remote-debugging`, then add the following config to your MCP client to attach to your running Brave:
 
 ```json
 {
   "mcpServers": {
     "brave-devtools": {
       "command": "npx",
-      "args": ["-y", "brave-mcp@latest"]
+      "args": ["-y", "brave-mcp@latest", "--autoConnect"]
     }
   }
 }
@@ -123,6 +129,8 @@ Add the following config to your MCP client:
 > [!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:
 
 ```json
@@ -140,7 +148,7 @@ See [Slim tool reference](./docs/slim-tool-reference.md).
 
 ### 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][client-configurations-guide].
+For setup instructions specific to your editor or agent (e.g. Antigravity, Claude Code, Cursor, VS Code), please see our [Client Configurations Guide][client-configurations-guide]. To attach to your running Brave, add `--autoConnect` to the server arguments shown there.
 
 ### Your first prompt
 
@@ -150,10 +158,10 @@ Enter the following prompt in your MCP Client to check if everything is working:
 Check the performance of https://brave.com
 ```
 
-Your MCP client should open the browser and record a performance trace.
+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 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.
+> 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.
 
 ## Tools