Apple ships a Safari MCP server in Safari 27 beta, delivered through safaridriver

Apple's WebKit team introduced the Safari MCP server on July 1, shipping it in Safari 27 beta and Safari Technology Preview 247. The server connects an MCP-compatible agent to a Safari browser window so the agent can see how code actually renders: it exposes the DOM, network requests, screenshots, and console output for development and debugging work.

Delivery is through the existing safaridriver binary rather than a separate install. The documented setup for Claude is claude mcp add safari-mcp -- "/usr/bin/safaridriver" --mcp, with an equivalent command for Codex and a plain JSON block for other clients. Using it requires enabling "Show features for web developers" and then "Allow remote automation and external agents" in Safari's settings.

The server exposes seventeen tools covering tab management (create_tab, close_tab, list_tabs, switch_tab), page inspection (get_page_content, page_info, browser_console_messages, list_network_requests, get_network_request), interaction (page_interactions, evaluate_javascript, navigate_to_url, wait_for_navigation, browser_dialogs), and rendering controls (screenshot, set_viewport_size, set_emulated_media).

The post states the server runs entirely on the local machine, makes no network calls of its own, and has no access to personal Safari data such as AutoFill; captured page content goes directly to the agent the user is running, not to Apple. The announcement names no spec revision, no transport, no license, and no source repository, so this record stays out of the adoption tracker until a separate probe confirms those details.