Back to reviews
Safari MCP

Safari MCP

80 native tools to automate Safari from your AI agent on macOS

Safari MCP is an open-source Model Context Protocol server that exposes 80 native macOS tools for automating Safari — covering everything from tab management and form filling to JavaScript execution, screenshot capture, and network request interception. Unlike Playwright or Puppeteer which spin up a Chromium subprocess, Safari MCP connects directly to a running Safari instance through AppleScript and the macOS Accessibility APIs, making it the only browser automation option that works with your actual logged-in Safari session, cookies, and extensions intact. The 80-tool scope is notable: most browser MCP implementations ship 10–20 tools focused on basic navigation. Safari MCP covers the full browser lifecycle — bookmark management, reading list, private browsing, download tracking, and even Safari's built-in translation feature. For macOS-heavy teams where Safari is the default browser (and where Chrome-based automation feels like bringing in a chainsaw to peel an apple), this fills a practical gap. It appeared on Hacker News with a small but enthusiastic audience — primarily macOS devs who've been watching the Chrome-centric browser automation ecosystem with mild frustration. The zero-dependency installation (no browser binary downloads, no npm build step) and the fact that it leverages Apple's own accessibility stack rather than reverse-engineering the browser protocol makes it an unusually clean approach.

Panel Reviews

The Builder

The Builder

Developer Perspective

Ship

Finally — a browser MCP that works with my actual session rather than a fresh sandboxed Chrome instance. For macOS workflows where I need the agent to interact with sites I'm already logged into, this is immediately useful.

The Skeptic

The Skeptic

Reality Check

Skip

AppleScript and Accessibility API automation is notoriously brittle across macOS updates — Apple has a habit of quietly breaking third-party accessibility automation without notice. I'd want to see macOS version compatibility guarantees before building any serious pipeline on this.

The Futurist

The Futurist

Big Picture

Ship

The pattern of 'connect to the user's real browser rather than a disposable sandbox' is the right direction for personal AI agents. As agents become more integrated with our daily digital lives, using our actual identity and context beats spinning up a clean slate every time.

The Creator

The Creator

Content & Design

Ship

Being able to point Claude at my actual Safari with my actual logins to help me research and interact with sites I use daily is a real quality-of-life win. This is the kind of 'just works with my setup' tool I actually reach for.

Community Sentiment

Overall235 mentions
65% positive28% neutral7% negative
Hacker News95 mentions
68%25%7%

Real session vs sandboxed browser debate

Reddit60 mentions
62%30%8%

macOS-native automation without Chromium dependency

Twitter/X80 mentions
65%28%7%

Safari finally gets proper MCP support