The Safari MCP server for web developers

Apple just dropped a new feature in Safari’s test version that lets an AI coding assistant peek directly into a Safari browser window while a developer works. In plain English: instead of bouncing between code, browser tabs, screenshots, and frantic copy-pasted prompts, the helper can now see what the page actually looks like, read error messages, check loading speed, and even spot some accessibility problems on its own. That’s the sales pitch, anyway.

The comment section, of course, instantly turned into a mix of applause, side-eye, and opportunism. One early reaction summed up the vibe with deadpan calm: this is basically a mashup of browser tools and large language models, and somehow that “sounds sane enough.” That may be the most restrained anyone has ever been about giving AI more power. Others immediately skipped the productivity angle and went straight to the chaos goblin use case: one commenter wondered whether Apple’s Private Relay could help dodge scraping blocks if sites already trust Apple traffic. Yes, the internet noticed that part fast.

And then came the competitive chest-thumping. A few developers basically replied, “Cute, Chrome already does this,” with one saying they’ve been using Chrome’s official version for months and even sending AI to test pages in Firefox too. Another popped in with a link to their own similar project, casually turning the thread into a mini product showdown. Meanwhile, one practical soul asked the question many Apple developers probably care about most: can it handle mobile Safari simulation too? So the mood is clear: interest, rivalry, and just enough mischief to keep it spicy.