macos-automator-mcp
Lets MCP clients discover and run AppleScript or JavaScript for Automation (JXA) to control macOS applications, inspect the system, or reuse scripts from a bundled knowledge base.
README
macOS Automator MCP 🤖 — Give your agent a Mac to operate

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 may prompt for macOS permissions.
Tools
| Tool | Purpose |
|---|---|
get_scripting_tips |
List knowledge-base categories or search for AppleScript and JXA tips. |
execute_script |
Run one inline script, script file, or knowledge-base script ID. |
Use get_scripting_tips before writing a script from scratch. A returned runnable ID can be passed to execute_script as kb_script_id; scripts with placeholders accept named input_data or positional arguments.
execute_script runs with the privileges of the process hosting the MCP server. Only run scripts you trust, and inspect generated scripts before allowing destructive actions. See the tool reference for every input and response option.
Permissions
The application that launches the MCP server—such as Terminal, an editor, or a desktop MCP client—owns its macOS privacy permissions:
- Grant Automation access when scripts control Finder, Safari, Mail, or another application.
- Grant Accessibility access when scripts use System Events for clicks, keystrokes, menus, or other UI scripting.
macOS may show a first-use prompt for each target application. The server cannot grant these permissions itself. See configuration and permissions for setup and common error codes.
Knowledge base
The package includes hundreds of AppleScript and JXA tips covering system tasks, files, browsers, terminals, productivity apps, developer tools, and UI automation. Search by keyword or category, then execute a result by its runnable ID.
A local knowledge base can add or override bundled tips without changing the package. It defaults to ~/.macos-automator/knowledge_base; see configuration and permissions for its layout and override rules.
Configuration
| Variable | Values | Default |
|---|---|---|
LOG_LEVEL |
DEBUG, INFO, WARN, ERROR |
INFO |
KB_PARSING |
lazy, eager |
lazy |
LOCAL_KB_PATH |
Absolute path to a custom knowledge base | ~/.macos-automator/knowledge_base |
lazy loads the knowledge base on first use; eager loads it at server startup. More detail is in configuration and permissions.
Troubleshooting
- Permission errors such as
-1743or-10004usually mean the host application needs Automation or Accessibility access. - Script syntax errors are easiest to isolate with
include_executed_script_in_outputandinclude_substitution_logs, then reproduce in Script Editor. - Use an absolute POSIX path with
script_path, and raisetimeout_secondsfor scripts that legitimately need more than 60 seconds. - JXA normally works best with
output_format_mode: "direct"; the defaultautomode selects it for JXA.
See Debugging AppleScript and JXA for a longer diagnostic guide.
Development
pnpm install
pnpm run build
pnpm test
pnpm run lint
pnpm run validate
The repository uses pnpm 11 and Node.js 24. The development guide covers local server setup and knowledge-base contributions.
Community
Report bugs and propose scripts in GitHub Issues.
<a href="https://glama.ai/mcp/servers/@steipete/macos-automator-mcp"> <img width="380" height="200" src="https://glama.ai/mcp/servers/@steipete/macos-automator-mcp/badge" alt="macOS Automator MCP server on Glama" /> </a>
License
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。