Safari MCP — 80 tools for native macOS browser automation (no Chrome, no Puppeteer)

[achiya-automation]

Every MCP browser server I found required Chrome. On my MacBook, that meant a second browser process burning CPU while Safari sat right there with all my sessions already loaded. So I built an MCP server that uses Safari natively. What it does: Safari MCP gives AI agents 80 tools for browser automation — navigation, clicking, form filling, screenshots, network capture, cookies/storage, accessibility snapshots, device emulation, and more — all running through AppleScript + a Swift daemon on macOS. Why it exists: - Your Safari already has all your logins (Gmail, GitHub, Slack, dashboards). No re-authenticating. - On Apple Silicon, native WebKit uses ~40-60% less CPU than Chrome. - Zero dependencies beyond Node.js 18+. Quick comparison: | | Safari MCP | Chrome DevTools MCP | Playwright MCP | |---|---|---|---| | Your existing logins | Yes | Yes | No | | CPU overhead | Minimal | High | Medium | | Dependencies | None | Chrome + debug port | Playwright runtime | | Tool count | 80 | ~30 | ~25 | Install: bash npm install safari-mcp MCP config: json { "mcpServers": { "safari": { "command": "npx", "args": ["safari-mcp"] } } } One-time: Safari > Settings > Advanced > Show features for web developers, then Develop > Allow JavaScript from Apple Events. Tested with Claude Code, Claude Desktop, Cursor, Windsurf, VS Code + Continue. MIT licensed. Links: GitHub · npm --- For anyone on macOS — do you use Safari as your main browser but find yourself forced into Chrome for automation? Curious what workarounds others have found.