Safari 27 Unveiled: What Developers Need to Know

Apple’s latest Safari release, version 27, is finally here and the WebKit blog has taken the time to walk us through the bits that actually matter to developers. It’s not just another incremental update – there’s a whole new automation story, plus a raft of enhancements that feel like a breath of fresh air.

The MCP server is the headline act. In plain English, MCP (short for Multi‑Client Protocol) is a lightweight server that runs on your own Mac. Once you flip on Allow remote automation and external agents in Safari → Settings → Developer, any AI‑powered coding assistant – think Claude Code, OpenAI Codex, or a custom bot you’ve built – can take the wheel. The agent can inspect the DOM, sniff network traffic, grab screenshots, read console output and even interact with forms, all without you constantly hopping between windows.

Apple is quick to point out that the MCP server never talks to the internet on its own, never sifts through your personal Safari data, and streams any captured info straight to the agent you’re running. In other words, it’s a local‑only helper that respects privacy – something that feels reassuring in today’s privacy‑first world.

Getting it set up is almost painless. First, enable “Show features for web developers” under Safari → Settings → Advanced; then the Developer pane appears, where you can tick the remote automation box. After that, you follow the command snippets Apple supplies to hook your preferred AI model to the server. It’s a tiny bit of extra ceremony for a huge productivity boost.

Beyond MCP, Safari 27 brings a mountain of other goodies. Apple claims nearly 850 bugs have been squashed – up from the 525 fixes announced at WWDC a few months back. The fixes touch everything from accessibility quirks and CSS rendering bugs to MathML handling, WebRTC stability, and font‑loading hiccups.

One of the more exciting visual upgrades is support for immersive environments. Developers can now serve visionOS‑ready experiences straight from Safari, meaning you can craft AR/VR‑like content that lives inside Apple’s mixed‑reality headset without a separate app. It’s a subtle nudge toward a more platform‑agnostic web.

Hand‑in‑hand with that is the expanded HTML <model> element, which finally rolls out to iOS, iPadOS and macOS. Think of it as the web’s answer to embedding interactive 3‑D assets – you can drop a model onto a page just like you would an image or video, and users can rotate, zoom, or even animate it on the fly.

Scrolling got a tiny but welcome makeover with Scroll Anchoring. No more jarring jumps when an image loads above your viewport; Safari now keeps the content you’re looking at glued in place. It’s a subtle polish that makes long‑form reading feel smoother.

The Web Inspector also got a makeover. There’s now inline color‑contrast info (so you can see accessibility warnings at a glance), clearer redirect‑chain visualization, and better layout‑debugging tools. If you spend half your day in the inspector, you’ll notice the difference immediately.

Under the hood, Safari 27 continues to push the envelope on modern web standards: WebAssembly, WebGPU, JavaScript, CSS, media playback, Service Workers, and WKWebView all see performance tweaks or new APIs. It’s a reminder that Apple is still heavily invested in keeping Safari a first‑class platform for cutting‑edge web work.

All in all, Safari 27 feels less like a “just‑another‑browser‑update” and more like a developer‑centric refresh. Whether you’re leaning on AI agents to speed up debugging or you’re building the next immersive web app, there’s something here worth digging into.