With the general release of Safari 27 on September 14, Apple became the first maker of a mainstream browser to ship a native MCP (Model Context Protocol) server. Any MCP-compatible client — Claude Code, Codex CLI, Gemini, or Cursor among others — can now connect directly to a real Safari window without installing third-party bridges or adapters.
The server exposes 15 tools that give an agent access to DOM inspection and manipulation, reading the console message buffer, network request detail (headers, timing, bodies), screenshot capture and content extraction, JavaScript evaluation, browser dialog handling, tab and viewport control, and accessibility and performance analysis. In practice, an agent can open a tab, navigate, read console errors, and run debugging actions from a single prompt — with no need for Chrome or a separate automation stack running in the background.
It's not exposed by default or silently: it requires an explicit two-step activation. First, under Safari > Settings > Advanced, you have to check "Show features for web developers"; then, under Safari > Settings > Developer, you have to check "Allow remote automation and external agents." The technical setup runs through safaridriver --mcp, configurable via command line or config files.
Apple documents that the server runs entirely on the local machine and makes no network calls of its own, and that the agent operates in a dedicated automation window, separate from the user's personal session — with no access to cookies, passwords, AutoFill, or browsing history.
Carlos Montiel is an enterprise AI solutions architect. He implements LLMs, Agents, RAG, and orchestrators for businesses in Guatemala and Latin America. Reach out for a consultation.
Contact Carlos Montiel