Apple ships a Safari MCP server
Apple's Safari MCP server exposes 14 local tools to AI agents: DOM inspection, JS evaluation, screenshots, and page interaction, with no Apple network calls.
Apple released an official MCP server for Safari on July 1 as part of Safari Technology Preview 247. The server exposes 14 tools to AI coding agents and assistants: page navigation and tab management, DOM inspection, JavaScript evaluation, network request monitoring, screenshots, and page interaction including clicking, typing, scrolling, and hovering. Viewport emulation for responsive testing is included.
All operations run locally. The Safari MCP server makes no network calls back to Apple, and agent access is scoped to tabs the developer has opened for tool use, not the full browsing session.
For operators running web agents or automating browser-based workflows, the practical effect is that Claude, Cursor, and other MCP-compatible clients can now drive Safari natively without a third-party browser bridge. Apple joining the MCP spec directly adds durable platform support to what has until now been a patch of third-party adapters. The Cursor MCP Marketplace announced this week shows how quickly that ecosystem assembles clients.
The local-only architecture matters for data handling. Browser sessions contain session cookies, authenticated content, and form data. Unlike remote browser automation services, nothing leaves the machine. That fits the constraint in securing your MCP integrations: know what each server can read before wiring it to an agent, and scope access to the minimum tabs needed.
Safari Technology Preview ships to developers who opt in. A stable Safari release date was not announced.