The Coyote MCP Server executes AppleScript commands on macOS through the Model Context Protocol (MCP), enabling comprehensive system automation. Key capabilities include:
Run AppleScript Code: Execute any AppleScript command using the
run_applescripttoolDisplay System UI: Show custom dialogs and notifications
Application Control: Launch and manage applications like Calculator and Safari
Web Browser Automation: Open browsers and navigate to specific URLs
File System Integration: Interact with files, folders, and perform various macOS automation tasks
Enables execution of AppleScript commands on macOS systems, allowing automation of system operations, application control, and user interface interactions through the native AppleScript scripting language.
Coyote MCP Server
A Model Context Protocol (MCP) server that enables AppleScript execution on macOS through the run_applescript tool.
Quick Start
Usage Commands
Interactive Mode (Recommended):
Then type any command like:
Use AppleScript to show a dialog with 'Hello World'Use AppleScript to open CalculatorUse AppleScript to open Safari and go to google.com
Quick Commands:
Note: Claude CLI will ask for permission before executing AppleScript commands. Grant permission when prompted to allow automation.
Quick Setup Commands
Client | Setup Command |
Claude CLI |
|
Claude Desktop |
|
VS Code |
|
Windsurf |
|
Cursor |
|
All clients |
|
After Setup
Once setup is complete, you'll see the MCP server listed as coyote-use in your client:
Claude CLI/Desktop: Server appears in MCP configuration
VS Code: Available in MCP extension as
coyote-useWindsurf: Available in Cascade → Plugins as
coyote-useCursor: Server appears in MCP configuration as
coyote-use
The server provides the run_applescript tool for executing AppleScript commands on macOS.
Uninstall
To completely remove Coyote MCP Server and all configurations:
This will:
Remove
coyote-useserver from all MCP client configurationsUninstall the global npm package
Clean up binary files from system PATH
Create backup copies of modified configurations
Clean npm cache and old backup files
Troubleshooting
Command not found error after update: