TL;DR: Use your real Safari with all your logins, cookies, and sessions. No headless browsers, no Chrome, no Puppeteer. Just pure AppleScript + JavaScript running natively on macOS — 60% less CPU/heat on Apple Silicon.

Highlights

• 80 tools — navigation, clicks, forms, screenshots, network, storage, accessibility, and more
• Zero heat — native WebKit on Apple Silicon, ~60% less CPU than Chrome
• Your real browser — keeps all logins, cookies, sessions (Gmail, GitHub, Ahrefs, etc.)
• Background operation — Safari stays in the background, no window stealing
• No dependencies — no Puppeteer, no Playwright, no WebDriver, no Chrome
• Persistent process — reuses a single osascript process (~5ms per command vs ~80ms)
• Framework-compatible — React, Vue, Angular, Svelte form filling via native setters

Quick Start

Prerequisites

• macOS (any version with Safari)
• Node.js 18+
• Safari → Settings → Advanced → Show features for web developers ✓
• Safari → Develop → Allow JavaScript from Apple Events ✓

Install

git clone https://github.com/achiya-automation/safari-mcp.git
cd safari-mcp
npm install

Configure

Add to your MCP client config:

{
  "mcpServers": {
    "safari": {
      "command": "node",
      "args": ["/path/to/safari-mcp/index.js"]
    }
  }
}

{
  "mcpServers": {
    "safari": {
      "command": "node",
      "args": ["/path/to/safari-mcp/index.js"]
    }
  }
}

{
  "mcpServers": {
    "safari": {
      "command": "node",
      "args": ["/path/to/safari-mcp/index.js"]
    }
  }
}

{
  "mcpServers": {
    "safari": {
      "command": "node",
      "args": ["/path/to/safari-mcp/index.js"]
    }
  }
}

Tools (80)

Navigation (4)

Page Reading (3)

Click & Interaction (5)

Form Input (7)

Screenshots & PDF (3)

Scroll (3)

Tab Management (4)

Wait (2)

JavaScript (1)

Element Inspection (4)

Accessibility (1)

Drag & Drop (1)

File Operations (2)

Dialog & Window (2)

Device Emulation (2)

Cookies & Storage (10)

Clipboard (2)

Network (6)

Console (4)

Performance (2)

Data Extraction (4)

Advanced (5)

Automation (1)

Safari MCP vs Alternatives

Tip: Use Safari MCP for daily browsing tasks (95% of work) and Chrome DevTools MCP only for Lighthouse/Performance audits.

Architecture

Claude/Cursor/AI Agent
        ↓ MCP Protocol (stdio)
   Safari MCP Server (Node.js)
        ↓ Persistent osascript process (~5ms/cmd)
   AppleScript → Safari
        ↓ do JavaScript in tab N
   Page DOM (your real browser)

Key design decisions:

• Persistent osascript process — one long-running process instead of spawning per command (16x faster)
• Tab-indexed operations — all JS runs on a specific tab by index, never steals visual focus
• JS-first approach — typing, clicking, file upload all use JavaScript events (no System Events keyboard conflicts)
• No activate — Safari is never brought to foreground

macOS Permissions

Safari MCP needs these one-time permissions:

Troubleshooting

Works With

Safari MCP works with any MCP-compatible client:

Contributing

PRs welcome! The codebase is two files:

• safari.js — Safari automation layer (AppleScript + JavaScript)
• index.js — MCP server with tool definitions

Star History

If Safari MCP saved you from Chrome overhead, consider giving it a ⭐

License

MIT — use it however you want.