Claude Control your Mac connectorWhat Claude can do in your Control your Mac account.
The Claude Control your Mac connector exposes 1 tool: 0 read, 1 write. That tool has your Mac run AppleScript commands that Claude writes. Below: what it can change on your machine, what nobody documents, and who stays in control.
Verified Trustpilot reviews · AI, automation & growth agency
What changes on your Mac
AppleScript is the scripting language Apple built into macOS to drive apps and the system. With this extension you don't need to know it: you tell Claude what you want, it writes the command and has your Mac run it through osascript, the system program that launches those scripts.
Drive an app without hunting for it. The extension's author lists controlling applications as the first use: you ask, Claude drafts the script, and osascript runs it.
Flip a system setting. The second use the author mentions: adjusting macOS settings from the conversation instead of digging through preference panes.
Chain a small repetitive chore. More broadly, the author pitches the tool as a way to automate tasks on macOS, as long as AppleScript can describe them. You stay the one deciding which chore is worth handing over.
What Claude can't do here: anything outside macOS, or on any machine other than the one where the extension lives. The author publishes no list of allowed or blocked commands and no described safeguards. And nothing runs by itself: no script fires at a set time or when a file lands. Scheduled jobs like that belong to an automation tool, a different line of work gathered on the Integrations hub.
The vocabulary in one minute
Five words to know before you install the extension.
- Connector
- The link you set up once between Claude and a service or tool you already use, so Claude can use it while it answers you.
- Tool
- A named capability the connector opens to Claude. Claude picks it on its own when it's needed; the directory sheet lists it by name.
- Authorization
- The access you hand Claude when you connect, granted once per person and taken back whenever you want by switching the connector off.
- Approval
- The confirmation Claude waits for before completing anything that changes something, shown in the conversation at the moment it matters.
- MCP
- The shared standard connectors run on: it's what lets an assistant like Claude talk to an outside service or program.
Plug Control your Mac into Claude in three steps
- 01
Find the extension
In Claude Desktop, open Customize, then Connectors, and look for Control your Mac in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Start the connection
Click Connect on its row and follow the window that opens. If the extension ever stops responding, use Disconnect, then connect it again from that same row.
- 03
Read what you accept
Read the authorization screen before you confirm: that screen, not Claude, sets what the access covers. This tool runs scripts on your machine, so take a moment to understand what you're opening up.
The single tool of the Claude Control your Mac connector
Control your Mac gives Claude 1 tool: 0 that read your account, 1 that change something in it.
One tool, filed under write because it runs commands that act on your machine. Its name stays as Claude shows it.
- 1 write
What Claude changes (1)
1 toolOne tool that acts on your Mac. No source describes a confirmation step of its own, so the general rule below applies.
osascript
Approval: see the ruleRuns an AppleScript command that Claude drafted on your Mac, as if you had typed it yourself. According to the author, that's how it drives applications or adjusts system settings.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before any action it takes for you. With a tool that runs code on your machine, that rule is what protects you.
On a Team or Enterprise workspace, owners decide whether a member can let certain actions through without being asked again. They can also cap what a connector does for the whole organization, and nobody bypasses that setting from their own account. And Claude works with your permissions, nothing more: whatever your macOS session isn't allowed to do, the script can't do either, no matter how the request is phrased.
Which plans it's available on
None of the 819 sheets in the official directory shows availability by plan. A connector-by-connector answer isn't published anywhere.
The general rule is sourced: desktop extensions install on Claude Desktop, open to all of its users, while remote connectors run on Claude, Cowork, Claude Desktop, and mobile. On Team and Enterprise, an Owner or Primary Owner enables them for the organization. For the current status, check the Control your Mac sheet in the official directory.
Where Control your Mac stops
A connector isn't an automation. Claude calls this tool while it answers you: no script starts by itself, on a schedule or on an event.
Only its author documents this extension, and thinly: a one-line manifest entry per tool and a build note. Neither Claude's help center nor Anthropic's documentation has a page about it. The directory badge isn't a security audit, and Anthropic writes on every sheet that it doesn't choose a publisher's tools and can't vouch for their behavior. The same reading grid applies to other sheets, such as the Claude affinity connector page.
Need help connecting Control your Mac to Claude?
A person reads every message.
