- Home
- Resources
- Integrations
- Brave (AppleScript)
Claude Brave (AppleScript) connectorWhat Claude can do in your Brave (AppleScript) account.
The Claude Brave (AppleScript) connector exposes 10 tools: 3 read, 7 act on the browser. Claude can list your tabs, read a page, open or close tabs and run scripts in Brave on a Mac. Below: what it reads, what it changes, what to review, and its limits.
Verified Trustpilot reviews · AI, automation & growth agency
Why let Claude drive Brave
Most research ends with a dozen tabs and a lot of copying and pasting. This desktop extension lets Claude work directly in the Brave browser on your Mac: it sees which tabs are open, reads the text of a page, opens the next address and closes what you no longer need. You keep talking in Claude Desktop, and the browser follows.
A summary of what is already open. You have six articles side by side. list_tabs shows Claude every open tab across your Brave windows, and get_page_content pulls the text of the ones you point at, so it can compare them in the chat.
A tidier browser in one sentence. Ask Claude to close the tabs you finished with: it finds them by ID, then close_tab shuts them one by one, while switch_to_tab brings the one you still need to the front.
A quick check on a live page. execute_javascript runs a script inside a tab, for instance to read a value the page computes. The extension's own README flags this as the part that reaches furthest, and the riskiest.
What it doesn't do: it is not Brave's official product (the sheet states it isn't affiliated with Brave Software), it only works on macOS with Brave installed, and it runs inside Claude Desktop. Nothing happens on its own either: Claude acts when you ask, never on a schedule. Recurring jobs are an automation tool's trade; the Integrations hub covers that side.
The vocabulary in one minute
Five words worth knowing before you hand Claude your browser.
- Connector
- The link you set up once between Claude and something you already use, here your Brave browser, so Claude can work with it while it answers.
- Tool
- One named job the connector opens to Claude, like closing a tab. Claude picks the tools it needs; the directory lists them by name.
- Authorization
- The step where you hand Claude the access it will use afterwards. Granted once per person, and it can be taken back the same way.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes things, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside app or service.
Connect Brave (AppleScript) to Claude in three steps
- 01
Find the extension in Claude
This is a desktop extension, so it lives in Claude Desktop. In Claude's settings, open Customize, then Connectors, and look for Brave (AppleScript). On a Team or Enterprise workspace, an Owner or Primary Owner turns it on first.
- 02
Start the connection
Click Connect on its row and follow the prompts. If the link breaks later, use Disconnect, then plug it back in; the access can also be removed from the other side whenever you want.
- 03
Read what you grant
Read the authorization screen before you accept. It decides what the access covers, and it may announce wider permissions than what Claude does day to day. The publisher's README says the extension gives wide control over your browser.
The 10 tools, sorted by what they do
Brave (AppleScript) gives Claude 10 tools: 3 that read your account, 7 that change something in it.
Three tools read what is in the browser, seven act on it. Names stay in English, exactly as Claude shows them.
- 3 read
- 7 write
Tools index
What Claude reads (3)
3 toolsThree tools that look at your tabs and pages without changing them.
get_current_tab
Tells Claude which tab is active right now, with its address, its title and its ID. That ID is what the other tools use to target a tab.
list_tabs
Returns every open tab across all your Brave windows, so Claude gets the full inventory before it reads, switches or closes anything.
get_page_content
Pulls the text of a web page into the conversation, which Claude can then quote, compare or condense. You get the words on the page, not a screenshot.
What Claude acts on (7)
7 toolsSeven tools that open, close, move or run things in Brave. No source details a confirmation for any of them: the general rule below applies.
open_url
Approval: see the ruleLoads an address in Brave, either in a fresh tab or in place of the current page, so Claude can bring up a site you mention.
close_tab
Approval: see the ruleShuts one tab, targeted by its ID; the README lists closing tabs among what the extension can do.
switch_to_tab
Approval: see the ruleBrings a given tab to the front by its ID, so the page you need is the one on screen.
reload_tab
Approval: see the ruleRefreshes the current tab or a specific one, so the page shows its latest state.
go_back
Approval: see the ruleSteps one page back in the history of a tab, as the browser's back arrow would.
go_forward
Approval: see the ruleThe reverse move: returns to the page you had just left in that tab's history, if there is one.
execute_javascript
Approval: see the ruleExecutes script code inside a tab. It can read what a page computes, and it can just as well change the page or act on it.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes on your behalf. For this extension, no source says which of the seven acting tools trigger a prompt.
The publisher's README is blunt: it warns the extension gives wide control over your browser, tells you to be careful with the commands you authorize, and to review every script before it runs. On Team and Enterprise, owners decide whether members can let some actions through without being asked each time, and they can restrict what a connector may do for the whole organization; nobody undoes that from their own account. And Claude never goes further than what the connected person can already do.
Which plans it's available on
None of the 819 sheets in the official directory states plan availability. For any single connector, that answer is published nowhere: a real gap in the catalogue.
The general rule is public. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install in Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches a connector on for the organization before members can link it. For the current state, the connector's sheet in the official directory is the place to check.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing opens or closes in Brave when you are not in the conversation.
All of the detail on this page comes from the publisher, an independent developer: no Claude help article covers this extension. The directory badge is not a security audit, and Anthropic writes on every sheet that it doesn't control the tools a developer exposes or guarantee they behave as described, so only plug in what comes from someone you trust. For a connector of another kind, compare with the Claude activecampaign connector page.
Need help connecting Brave (AppleScript) to Claude?
A person reads every message.