Debugging a website usually means a human hunched over DevTools, squinting at console errors and network waterfalls. Apple wants to hand some of that grunt work to your AI coding assistant instead. On July 1, 2026, the WebKit team shipped a new Safari MCP server as part of Safari Technology Preview 247, and it does exactly what the name hints at: it plugs coding agents straight into the browser so they can inspect and debug real pages.
MCP — the Model Context Protocol — is the increasingly common plumbing that lets large language models talk to external tools in a structured way. By exposing Safari through an MCP server, Apple gives agents a first-class window into what a webpage is actually doing, rather than making them guess from source code alone.
The practical upshot: an agent can now open a page and actually look. It can pull page content, read console logs, watch network requests, capture screenshots, and interact with elements directly on the page. That closes a frustrating gap. Instead of telling your assistant “the button isn’t working” and hoping it reasons its way to the bug, the agent can navigate to the page, click the button, catch the console error, and check the network call that failed — all on its own.
Apple documents 15 tools in total, covering the everyday scenarios a developer runs through by hand:
- Page navigation — moving the browser to and around a target site
- DOM inspection — reading the structure and content of the rendered page
- Visual verification — grabbing screenshots to confirm what actually shows up
- Accessibility auditing — checking pages against a11y expectations
That last one is worth flagging. Accessibility is the kind of task that’s easy to skip under deadline pressure, so baking an auditing tool into the agent’s toolkit nudges it toward being part of the normal loop rather than an afterthought.
A few caveats keep this grounded. Safari Technology Preview is a developer-focused build, deliberately kept separate from the Safari most people use every day. It’s where Apple tries out features before — if they survive internal testing — they graduate to stable Safari. Apple hasn’t said when, or whether, the MCP server makes that jump. For now it’s a preview-only tool aimed squarely at people building for the web.
It’s also a free developer feature, so there’s no price tag to weigh up — just a Technology Preview install and an MCP-capable agent.
The bigger picture is more interesting than any single tool. Browsers have long been black boxes to AI assistants; giving Safari a proper MCP interface turns it into something an agent can genuinely operate. If it lands in stable Safari, “the AI can’t see what the page is doing” stops being a good excuse for a stubborn bug.
