Applescript MCP Server

AppleScript MCP Framework. The applescript mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

A Model Context Protocol (MCP) server that lets you run AppleScript code to interact with Mac. This MCP is intentionally designed to be simple, straightforward, intuitive, and require minimal setup.

• Run AppleScript to access Mac applications and data
• 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 support via SSH

Its toolset

Everything the assistant can do here goes through one of these:

• Setup — The Setup tool exposed by this server
• Configuration — This allows your Docker container to execute AppleScript on the Mac host system. Make sure:

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Applescript's toolset — Setup, Configuration — is a fair guide to whether it matches your workflow. It is maintained by chatflowdev; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the applescript mcp server does with a few real requests.