Safari browser automation for AI agents — native macOS, zero Chrome overhead. 96 tools via AppleScript + JavaScript.
Safari browser automation for AI agents — native macOS, zero Chrome overhead. 96 tools via AppleScript + JavaScript. That is what the safari mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
Your AI drives the Safari you're already logged into — Gmail, GitHub, Ahrefs, Slack, banking.
safari-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 3 tools. What each one is for:
Strategy — ExampleCoordinates — x: 100, y: 200Prerequisites — The Prerequisites tool exposed by this serverThis sits in the browser automation group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Safari MCP's toolset — Strategy, Coordinates, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by achiya-automation; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Strategy | Example |
| Coordinates | x: 100, y: 200 |
| Prerequisites | The Prerequisites tool exposed by this server. |
Or edit `~/.mcp.json`:
```json
{
"mcpServers": {
"safari": {
"command": "npx",
"args": ["safari-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.