Safari 27 ships an MCP server that hands coding agents the DOM and console output

The pitch is fewer screenshots. "Your agent can do more on its own while you do less hopping between windows, less dropping screenshots in your terminal, and less typing prompts to describe what's not working," Apple wrote on the WebKit blog ^[6]. What gets granted is wider than the pitch. Access to the DOM, network requests, screenshots and console output is access to whatever that window happens to be rendering ^[2], and Apple's own task list includes verifying user states in forms, checkout flows and selections ^[7].

This is aimed at the front-end developer who already runs Claude Code or Codex and wants the agent to see the render ^[5]. Two settings stand between a stock Mac and an attached agent. The Developer pane stays hidden until someone enables "Show features for web developers" under Safari > Settings > Advanced ^[4], and the checkbox itself is "Allow remote automation and external agents" ^[3]. A developer has to go looking for both ^[17].

Apple says the server runs entirely on the local machine and makes no network calls of its own ^[8]. It also says the server has no access to personal information in Safari, and that captured data goes directly to the agent the developer is running, not to Apple ^[9]. What the agent does with a screenshot once it has one sits outside Apple's description, and the 9to5Mac summary of the post does not say whether the setting scopes an attached agent to particular windows or profiles ^[18].

For whoever signs off on developer machines, the artifact is local. Everything the server does happens on that machine ^[8], so the check is the settings pane on that Mac and the agent's own logs ^[19].

Most of 27.0 is repair work. Apple now counts nearly 850 fixed issues against the 525 it announced at WWDC ^[11], which is about 325 more, roughly 62 percent above the earlier figure ^[13]. The fixed areas include accessibility, CSS, forms, networking and WebRTC ^[12].

Start with whether the work needs rendered state or would be served by the source files: comparing computed styles and layout against other browsers, and testing contrast and ARIA attributes, need the render ^[7], while a refactor does not. Then ask whether that Mac's Safari holds live sessions to production consoles or customer accounts. Turn it on where the first answer is yes and the second is no. Where both are yes, keep the agent work in a Safari that has never been logged into anything you would mind it reading, and take the cost of pasting screenshots by hand everywhere else.

Apple's post lists the specific commands for connecting Claude Code, Codex or another agent, and asks developers for feedback and feature requests ^[10].