coyote

Coyote MCP Server enables executing AppleScript on macOS via the run_applescript tool exposed by the server. After you install and build the server, you interact with it through Claude tools or your MCP client by referencing the coyote-use server. The CLI-based workflow lets Claude (or compatible clients) prompt the MCP to run AppleScript commands on your Mac, such as opening applications, showing dialogs, or navigating to websites. You can test and run commands in two modes: an interactive mode where Claude uses the MCP configuration to accept natural language commands, and quick commands that directly print a specific AppleScript instruction to the MCP for execution.

Typical usage involves ensuring the MCP server is registered under the client as coyote-use, then issuing commands like: "Use AppleScript to show a dialog with 'Hello World'" or "Use AppleScript to open Calculator". The server processes these requests by invoking the AppleScript tool on macOS and returning the result or status back to the client. The setup supports multiple clients (Claude CLI/Desktop, VS Code, Windsurf, Cursor) and will surface the coyote-use server within each client after installation.

Prerequisites:

• macOS host (required for AppleScript execution)
• Node.js and npm installed
• Access to the repository (clone or download)

Installation steps:

1. Clone the repository and navigate into it: git clone https://github.com/Sai-Adarsh/coyote-mcp-server.git cd coyote-mcp-server

2. Install dependencies: npm install

3. Build the server (if the project provides a build step): npm run build

4. Set up clients to use the MCP server (optional but recommended):

   • Claude CLI/Desktop: npm run setup-claude-cli
   • Claude: npm run setup-claude
   • VS Code: npm run setup-vscode
   • Windsurf: npm run setup-windsurf
   • Cursor: npm run setup-cursor
   • To set up all clients at once: npm run setup-all

5. Start the server locally for testing (if a start script is provided): npm start

Notes:

• Ensure your macOS machine allows automation permissions for scripts invoked by the server.
• After installation, your MCP server should appear as coyote-use in supported clients.

Tips and common considerations:

• The server exposes the run_applescript tool for macOS automation. Make sure the macOS user running the commands has necessary permissions to control applications.
• If you update the server, run hash -r in your shell or restart clients to ensure MCP configurations refresh.
• The exact server path (path/to/server.js) should be replaced with the actual entry point of your built Node.js server as produced by the project’s build process.
• When troubleshooting, verify that the MCP client has the coyote-use server registered and that the client configuration points to the correct path/port if applicable.
• For environments where GUI prompts are blocked, ensure accessibility permissions or automation permissions are granted for the Node.js process.