Safari (local) logo

Safari (local)

Beta

Apple's Safari MCP server, built into Safari 27. It lets an agent drive Safari: open tabs, navigate, read pages, run JavaScript, click and type, take screenshots and read console logs and network requests.

  • Apple
  • Automation
  • Local
Runs
On the developer's Mac
Launched with
Command line
Platform
macOS
Publisher
Apple

How it works

Every agent request passes through Ferentin policy before it reaches Safari (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with /usr/bin/safaridriver --mcp.

Ferentin's endpoint agent finds Safari (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Safari (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Safari (local)

Apple's Safari MCP server ships with Safari 27 and Safari Technology Preview. It gives an agent 17 tools for working in the browser, from navigating and reading pages to running JavaScript and inspecting network requests. It runs on the Mac, makes no network calls of its own and cannot read personal information in Safari such as AutoFill or other browsing activity. Each developer turns it on in Safari's Developer settings.

Frequently asked about Safari (local)

How do I connect Safari (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Safari (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Safari (local) integration generally available?
The Safari (local) integration is currently beta on Ferentin.