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
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 wonder if it supports Private Relay. Private Relay is great for getting around scraping blocks because they explicitly whitelist apple private Relay ips.
so it's a crossover of dev tools and LLM? sounds sane enough i'd say
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
I'd personally suggest Playwright-CLI: https://github.com/microsoft/playwright-cli
It works much faster for me than the MCP servers I tried.