Federico Viticci went into a little more detail about what this means on MacStories, Mastodon, and the latest episode of the Connected podcast. It is also more approachable for laypeople.

Be sure to visit the links from the story, as well.

https://www.macstories.net/linked/safaris-new-mcp-server-is-...

https://mastodon.macstories.net/@viticci/116847167023618099

https://relay.fm/connected/610

I am especially hopeful for this for my daily stuff, not just testing.

Meaning, having a hopefully seamless way to perform some automations in the browser on my behalf but since it’s the browser I’m logged in to, it just makes the handoff between myself and the agent feel more seamless.

And that’s because I’ve used safari as my main browser, not chrome, because it isn’t as much of a battery hog.

I have been using Chrome's official MCP devtools server since Nov 2025.

https://github.com/ChromeDevTools/chrome-devtools-mcp

Before that I used Chrome web drivers but MCP is faster and more capable.

I also instruct LLMs to test my pages on Firefox using its official MCP to make sure they work in Firefox too:

https://github.com/mozilla/firefox-devtools-mcp

Now I will add Safari to the compatibility tests. cool

I'd personally suggest Playwright-CLI: https://github.com/microsoft/playwright-cli

It works much faster for me than the MCP servers I tried.

There has been the (Apple provided) safaridriver for a couple of years. It speaks WebDriver W3C and can be used to interact with a Safari instance.

But does Apple really care about web developers?

How do you test on Safari if you don’t have Apple devices?

How difficult can it be for Apple to make barebones virtual machines with just Safaris?

I've been telling agents to run Chrome and talk to it directly via the CDP recently and finding that to work very well.

How are the MCP servers compared to Playwright?

MCP for browser automation is interesting because Safari's WebKit engine is the one most AI agents can't easily drive (Playwright and Puppeteer are Chromium-first). Having an MCP server for it could fill a real gap in cross-browser testing for agent workflows.

> There are many ways to build for the web, both with and without AI. If AI is a part of your workflow, we think this tool will help make it even more productive. And if it isn’t, that’s OK too.

Crazy thing to say in 2026 where if you write code and not delegate every bit to an agent you're considered a noob by some people.

Does the websites get some flag or clue that this is an AI bot interacting?

should say "see how my website performs on safari"

so it's a crossover of dev tools and LLM? sounds sane enough i'd say

I wonder if it supports Private Relay. Private Relay is great for getting around scraping blocks because they explicitly whitelist apple private Relay ips.

Does this support mobile simulator safari too

[flagged]

[dead]

[flagged]

Building something similar for Chrome and Firefox browsers: https://github.com/DO-SAY-GO/WebCLI - a CLI not MCP. Tho am considering MCP for distribution, even tho agents love the CLI and the proof demos speak for themselves.

The reason I did not include Safari was there wasn't enough parity between its Safaridriver surface and what Bidi/CDP give now. Safari is doing Bidi tho, iirc. So ...soon perhaps. ;) ;p xx ;p