Best for
- Users of Claude Desktop who want to control their Mac via natural language
- Developers who need to automate common macOS tasks like managing calendar, notes, mail, and file system
- Users who want a simple MCP server with minimal setup
A
AppleScript MCP Server
Community
Execute AppleScript to get full control of your Mac
GitHub source repository ↗
41FMRS · D
AppleScript MCP Server is a simple, lightweight MCP server that gives control of your Mac via AppleScript. It offers multiple installation methods (Node.js, Python) and supports remote execution. However, it grants permission to execute arbitrary code, so users should be cautious and ensure they use it in a safe environment.
A Model Context Protocol (MCP) server that lets you run AppleScript code to interact with Mac. It is intentionally designed to be simple, straightforward, intuitive, and require minimal setup. The core code is less than 100 lines. It supports running AppleScript to access Mac applications and data, e.g., interact with Notes, Calendar, Contacts, Messages, and more; search for files using Spotlight or Finder; read/write file contents and execute shell commands. Remote execution is supported via SSH.
Tools
execute_applescript
Execute a piece of AppleScript code and return the result.
Setup
### Install with Claude Desktop:
#### Node.js
Add to your Claude Desktop config:
{
"mcpServers": {
"applescript_execute": {
"command": "npx",
"args": ["@peakmojo/applescript-mcp"]
}
}
}#### Python (uvx)
No clone needed — run directly from the git repo:
{
"mcpServers": {
"applescript_execute": {
"command": "uvx",
"args": ["--from", "git+https://github.com/peakmojo/applescript-mcp", "mcp-server-applescript"]
}
}
}#### Python (local development)
Clone the repo and use uv to run from source:
brew install uv
git clone https://github.com/peakmojo/applescript-mcp.gitThen configure:
{
"mcpServers": {
"applescript_execute": {
"command": "uv",
"args": ["--directory", "/path/to/your/repo", "run", "mcp-server-applescript"]
}
}
}Fit and risk
Not for
- Users who need remote execution without SSH setup (unless they configure SSH options)
- Users who need platform-agnostic control (server only runs on macOS)
- Production environments requiring advanced security sandboxing or auditing, since it allows arbitrary AppleScript execution
Required permissions
- Ability to execute AppleScript code, which can access apps and data on the Mac
- Access to file system (read/write files)
- Ability to execute shell commands
- Remote connection via SSH (if enabled)
Risks and side effects
- Executing arbitrary AppleScript may make system changes, including deleting files, modifying settings, or sending messages
- Access to sensitive data such as contacts, calendar, mail, and file contents
- If used with SSH remote execution, credentials could be exposed, and remote control could be abused
- AppleScript errors may cause unexpected behavior or system instability
Troubleshooting
- Ensure AppleScript support is enabled on macOS (usually enabled by default)
- If using SSH remote execution, ensure Remote Login is enabled on your Mac (System Settings → Sharing → Remote Login) and provide correct username and password
- If using Docker, make sure to use `host.docker.internal` as the remote host in the config
- Check MCP server logs for error messages
Use cases
Create reminders, e.g., 'Create a reminder for me to call John tomorrow at 10am'
Add meetings to calendar, e.g., 'Add a new meeting to my calendar for Friday from 2-3pm titled "Team Review"'
Create notes, e.g., 'Create a new note titled "Meeting Minutes" with today's date'
Find files, e.g., 'Show me all files in my Downloads folder from the past week'
Check system info, e.g., 'What's my current battery percentage?'
Manage applications, e.g., 'List all the currently running applications on my Mac'
Control media playback, e.g., 'Play my "Focus" playlist in Apple Music'
Take screenshots, e.g., 'Take a screenshot of my entire screen and save it to my Desktop'
Supported clients
Claude DesktopFull support