Which integrations are available for this server?

Interacts with Discord using Electron fallback with Chrome DevTools Protocol for UI automation. Provides optional Chrome DevTools Protocol fallback for deeper UI inspection of Electron apps (e.g., VSCode, Slack, Discord). Automates Figma actions such as exporting frames as PNG via UI automation and AppleScript. Automates macOS system tasks including AppleScript, JXA, shell commands, window management, clipboard, notifications, and more. Retrieves current URL and title, and performs other browser automation tasks. Interacts with Slack using Electron fallback with Chrome DevTools Protocol for UI automation.

How do I use mac-pilot-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mac-pilot-mcp toggle dark mode" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

mac-pilot-mcp

by leesgit

Overview Schema Related Servers Score Discussions

TypeScript

Local

The Problem

There are 7+ macOS automation MCP servers. None of them remember anything. Every session starts from zero — same trial and error, same failures, same wasted tokens.

Related MCP server: openowl

The Solution

Mac-Pilot is different. It learns from every interaction:

Success? The pattern is auto-saved as app-specific knowledge
Failure? The error is recorded so it won't repeat the same mistake
Multi-step workflow? Save it as a recipe — replay it in one call next time

Ships with 21 built-in recipes so you're productive from the first run.

Quick Start

Install

npm install -g mac-pilot-mcp

Connect to your AI client

claude mcp add mac-pilot -- mac-pilot-mcp

Or manually add to ~/.claude.json:

{
  "mcpServers": {
    "mac-pilot": {
      "command": "mac-pilot-mcp"
    }
  }
}

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "mac-pilot": {
      "command": "npx",
      "args": ["-y", "mac-pilot-mcp"]
    }
  }
}

Add to your MCP settings (.cursor/mcp.json):

{
  "mcpServers": {
    "mac-pilot": {
      "command": "npx",
      "args": ["-y", "mac-pilot-mcp"]
    }
  }
}

Add to your MCP config:

{
  "mcpServers": {
    "mac-pilot": {
      "command": "npx",
      "args": ["-y", "mac-pilot-mcp"]
    }
  }
}

Grant Permissions

Mac-Pilot needs Accessibility access for UI automation:

System Settings → Privacy & Security → Accessibility
Toggle ON for your terminal app (Terminal, iTerm2, VS Code, Cursor, etc.)
Restart the terminal

How It Works

You: "Export the current Figma frame as PNG"

┌─ First time ─────────────────────────────────────────┐
│                                                       │
│  1. mac_recipe_search("Figma export") → No matches   │
│  2. mac_state() → Figma is frontmost                 │
│  3. mac_run(applescript) → File > Export > PNG        │
│  4. mac_recipe_save("export-figma-png", steps=[...]) │
│                                                       │
│  ✓ Worked! Pattern saved automatically.              │
└───────────────────────────────────────────────────────┘

┌─ Next time ───────────────────────────────────────────┐
│                                                       │
│  1. mac_recipe_search("Figma export")                │
│     → Found: export-figma-png (100% success rate)    │
│  2. mac_recipe_run("export-figma-png")               │
│     → Done instantly                                  │
│                                                       │
│  ⚡ 4 steps → 2 steps. No trial and error.           │
└───────────────────────────────────────────────────────┘

Tools

Tool	What it does
`mac_run`	Execute AppleScript, JXA, shell commands, open apps/URLs, click, type, keypress
`mac_state`	Query system state — frontmost app, windows, clipboard, running apps
`mac_find_ui`	Find UI elements via Accessibility API (buttons, fields, menus)
`mac_screenshot`	Capture screen/window/region as base64 PNG
`mac_recipe_save`	Save a working action sequence as a reusable recipe
`mac_recipe_run`	Replay a saved recipe with parameter substitution
`mac_recipe_search`	Full-text search across recipes and action history

Built-in Recipes

21 recipes ship out of the box — no setup needed:

Category	Recipes	Example
System	`toggle-dark-mode` `set-volume` `mute-toggle` `lock-screen` `show-desktop` `screenshot-desktop` `empty-trash` `get-dark-mode`	`mac_recipe_run { name: "toggle-dark-mode" }`
Finder	`new-finder-window` `get-selected-files`	`mac_recipe_run { name: "new-finder-window", params: { path: "/tmp" } }`
Safari	`safari-current-url` `safari-current-title`	`mac_recipe_run { name: "safari-current-url" }`
Clipboard	`get-clipboard` `set-clipboard`	`mac_recipe_run { name: "set-clipboard", params: { text: "Hello" } }`
Notifications	`notify`	`mac_recipe_run { name: "notify", params: { title: "Done", message: "Build passed" } }`
Terminal	`open-terminal-at` `kill-process`	`mac_recipe_run { name: "open-terminal-at", params: { path: "~/dev" } }`
Windows	`list-windows` `close-front-window`	`mac_recipe_run { name: "close-front-window" }`
Music	`music-play-pause` `music-next-track`	`mac_recipe_run { name: "music-play-pause" }`

Examples

AppleScript

{ "actionType": "applescript", "script": "tell application \"Finder\" to get name of every window" }

JXA (JavaScript for Automation)

{ "actionType": "jxa", "script": "Application('Safari').documents[0].url()" }

Shell command

{ "actionType": "shell", "command": "ls -la ~/Desktop" }

Open an app or URL

{ "actionType": "open", "target": "Safari" }
{ "actionType": "open", "target": "https://github.com" }

Type text

{ "actionType": "type", "text": "Hello World" }

Keyboard shortcut

{ "actionType": "keypress", "text": "cmd+c" }
{ "actionType": "keypress", "text": "cmd+shift+4" }

Find UI elements

mac_find_ui { "app": "Safari", "role": "AXButton" }
mac_find_ui { "app": "Finder", "searchText": "Downloads" }

Electron apps (VSCode / Cursor / Slack / Discord) — macOS Accessibility exposes a thin tree for Electron, so Mac-Pilot can optionally fall back to Chrome DevTools Protocol when the app is launched with --remote-debugging-port=<PORT>. See docs/ELECTRON-SUPPORT.md.

mac_find_ui {
  "app": "Visual Studio Code",
  "searchText": "Run Test",
  "useElectronFallback": "auto"
}

Take a screenshot

mac_screenshot { "target": "screen", "scale": 0.3 }
mac_screenshot { "target": "window", "windowName": "Safari" }

Save a custom recipe

mac_recipe_save {
  "name": "open-project",
  "description": "Open VS Code at project directory",
  "steps": [
    { "actionType": "shell", "params": { "command": "code {{path}}" }, "description": "Open VS Code" }
  ],
  "parameters": [
    { "name": "path", "description": "Project directory path" }
  ],
  "tags": ["dev", "vscode"]
}

Security

Mac-Pilot blocks dangerous operations before they execute:

Layer	Protection
Hard block	`sudo`, `rm -rf /`, `curl\|sh`, `dd if=`, `$()` subshell injection, keychain access, `csrutil disable`, `diskutil erase`, and 20+ patterns
Risk classification	Every action is rated `low` / `medium` / `high` / `blocked`
Audit log	All actions (including blocked ones) are logged to SQLite
Dry run	Test any action with `dryRun: true` before executing
Auto-cleanup	Action logs older than 30 days are pruned automatically

Architecture

~/.mac-pilot/pilot.db (SQLite, WAL mode)
├── action_log       — Every action executed, with timing + success/failure
├── action_log_fts   — Full-text search index over action history
├── recipes          — Saved automation sequences
├── recipes_fts      — Full-text search index over recipes
├── app_knowledge    — Per-app quirks, selectors, workarounds (auto-learned)
└── security_log     — Blocked command audit trail

Built-in recipes are auto-loaded on first run. Your custom recipes and learned knowledge persist across sessions.

Comparison

Feature	mac-pilot-mcp	Other MCP servers
Self-learning (auto-saves knowledge)	Yes	No
Reusable recipes with parameters	Yes	No
Built-in recipe library	21	0
JXA + AppleScript	Both	Usually one
Full-text search (recipes + history)	Yes	No
Security audit log	Yes	Rare
Risk classification (4 levels)	Yes	No
Dry run mode	Yes	Rare
Action log auto-cleanup	Yes	No

Troubleshooting

Your terminal needs Accessibility permission:

System Settings → Privacy & Security → Accessibility
Toggle ON for your terminal
Restart the terminal app completely

The target app must be running. Open it first:

mac_run { "actionType": "open", "target": "AppName" }

Reduce the scale (default is 0.5):

mac_screenshot { "target": "screen", "scale": 0.3 }

Recipe names are case-sensitive. Search first:

mac_recipe_search { "query": "your keyword" }

Use dry run to check the risk classification:

mac_run { "actionType": "shell", "command": "your-command", "dryRun": true }

Requirements

macOS (darwin only)
Node.js >= 18
Accessibility permission for UI automation

Contributing

Issues and PRs welcome at github.com/leesgit/mac-pilot-mcp.

git clone https://github.com/leesgit/mac-pilot-mcp.git
cd mac-pilot-mcp
npm install
npm run build
npm test        # 144 tests

License

MIT - Byeongchang Lee

This server cannot be installed

license - permissive license

quality - not tested

maintenance

How are these scores calculated?

Maintenance

–Maintainers

–Response time

0dRelease cycle

2Releases (12mo)

Commit activity

Resources

Need Help?

Related Servers

Latest Blog Posts

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leesgit/mac-pilot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server