A side-by-side look at the Applescript MCP and MCP Macos MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Applescript MCP for os automation work as a local process; choose MCP Macos for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Applescript MCP when
You need dedicated capabilities in the OS Automation domain.
No tool names declared yet. Check the project README from the listing page.
MCP Macos tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Applescript MCP is categorized under OS Automation and uses a local stdio subprocess. MCP Macos belongs to OS Automation and uses a local stdio subprocess. Pick Applescript MCP for os automation work and MCP Macos for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Applescript MCP is listed as free. MCP Macos has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add peakmojo-applescript-mcp and mcp-macos as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Applescript MCP has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 465 GitHub stars. MCP Macos has 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.