Atlas / MCP servers / steipete / MacOS Automator

MacOS AutomatorSAFE

Name: MacOS Automator
Author: steipete

mcp/steipete/macos-automator

MCP server by steipete · Audited 2026-09-26

⚑ Report / re-scan Source ↗

An MCP server to run AppleScript and JXA (JavaScript for Automation) to macOS.

Verdict

SAFE

Grade

Trust score

85 /100

Exposed tools

2 1r · 1w · 0d

Transport

stdio

License

MIT

Stars

885

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://github.com/steipete/macos-automator-mcp/actions/workflows/ci.yml) [](https://www.npmjs.com/package/@steipete/macos-automator-mcp) [](https://nodejs.org/) [](https://www.apple.com/macos/) [](LICENSE)

macOS Automator MCP is a Model Context Protocol server that lets MCP clients discover and run AppleScript or JavaScript for Automation (JXA). It is for agents that need to control macOS applications, inspect the system, or reuse scripts from a bundled knowledge base.

Install

You need macOS and Node.js 24 or newer. Add the server to your MCP client's configuration; npx downloads the current npm release when the client starts it.

{
"mcpServers": {
"macos_automator": {
"command": "npx",
"args": ["-y", "--package", "@steipete/macos-automator-mcp", "macos-automator-mcp"]
}
}
}

If your client has a separate package field, use @steipete/macos-automator-mcp without @latest.

Quick start

Restart your MCP client after adding the configuration. First, ask it to call get_scripting_tips with a small search:

{
"search_term": "Safari front tab URL",
"limit": 3
}

Then verify script execution with a read-only inline script through execute_script:

{
"script_content": "return \"Hello from macOS Automator\""
}

The result is Hello from macOS Automator. Calls that control applications or the user interface

Read from source at commit cc174102c3aaOBSERVED · 2026-09-26

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code

claude mcp add macos-automator-mcp -- npx -y @steipete/[email protected]

claude-desktop

{
  "mcpServers": {
    "macos-automator-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@steipete/[email protected]"
      ]
    }
  }
}

Exposed tools (2)

1 read · 1 write · 0 destructive.

Tool	Risk	Description
`execute_script`	write
`get_scripting_tips`	read

Trust audit

SAFEgrade B · trust 85/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

Layer	What it checks	Result
L0	Provenance & inventory	WARN
L1	Static analysis of the code	PASS
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	PASS
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: none-observed
Network: none-observed
Shell: none-observed
Dependencies: not all pinned
Secrets in source: none-found

Findings (13)

MEDIUMInventory / provenance · inv.symlink · CWE-1104

.windsurfrules

.windsurfrules

Why it matters. link not followed

LOWInventory / provenance · inv.symlink · CWE-1104

CLAUDE.md

CLAUDE.md

Why it matters. link not followed

LOWSupply chain · supply.unpinned · CWE-829, CWE-1357

package.json

@modelcontextprotocol/sdk, fuse.js, gray-matter, zod, @types/node, oxfmt, oxlint, tsx

Why it matters. 10 dependency range(s) float

Fix. pin exact versions or ship a lockfile