Skip to main content
Glama
Sai-Adarsh

Coyote MCP Server

by Sai-Adarsh
README.md
# Coyote MCP Server

A Model Context Protocol (MCP) server that enables AppleScript execution on macOS through the `run_applescript` tool.

## Quick Start

```bash
git clone https://github.com/Sai-Adarsh/coyote-mcp-server.git
cd coyote-mcp-server
npm install
npm run build
npm run setup-claude-cli  # or setup-claude, setup-vscode, setup-windsurf, setup-cursor
```

## Usage Commands

**Interactive Mode (Recommended):**
```bash
claude --mcp-config ~/.config/claude-cli/mcp.json
```
Then type any command like:
- `Use AppleScript to show a dialog with 'Hello World'`
- `Use AppleScript to open Calculator`
- `Use AppleScript to open Safari and go to google.com`

**Quick Commands:**
```bash
# Test the setup
claude --mcp-config ~/.config/claude-cli/mcp.json --print "Use AppleScript to show a dialog with 'Hello World'"

# Open applications
claude --mcp-config ~/.config/claude-cli/mcp.json --print "Use AppleScript to open Calculator"
claude --mcp-config ~/.config/claude-cli/mcp.json --print "Use AppleScript to open Safari"

# Navigate websites
claude --mcp-config ~/.config/claude-cli/mcp.json --print "Use AppleScript to open Safari and go to google.com"

# Create notifications
claude --mcp-config ~/.config/claude-cli/mcp.json --print "Use AppleScript to show a notification with title 'Test' and message 'Hello from MCP'"
```

**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 | `npm run setup-claude-cli` |
| Claude Desktop | `npm run setup-claude` |
| VS Code | `npm run setup-vscode` |
| Windsurf | `npm run setup-windsurf` |
| Cursor | `npm run setup-cursor` |
| All clients | `npm run setup-all` |

## 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-use`
- **Windsurf**: Available in Cascade → Plugins as `coyote-use`
- **Cursor**: 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:

```bash
npm run uninstall
# or
./uninstall.sh
```

This will:
- Remove `coyote-use` server from all MCP client configurations
- Uninstall 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:**
```bash
hash -r
```

## Development

```bash
npm run build    # Build the server
npm start        # Start manually for testing
```

## References

- [TypeScript MCP SDK](https://github.com/modelcontextprotocol/typescript-sdk)
- [MCP Protocol Overview](https://modelcontextprotocol.io/docs/learn/architecture)
- [Build an MCP Server](https://modelcontextprotocol.io/docs/develop/build-server)

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

Since there is only a single tool, naming consistency is inherently perfect; there are no other tool names to compare it against, so no inconsistencies can arise.

Tool Count2/5

A single tool is generally too few for most server purposes, as it limits functionality and suggests a very narrow scope. While it might be appropriate for a minimal utility, it often feels thin and incomplete for broader use cases.

Completeness1/5

The server's domain appears to be AppleScript execution on macOS, but with only one tool, there are significant gaps; for example, there are no tools for validating scripts, handling errors, or managing script files, making the surface severely incomplete for typical workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues