Apple is now the second browser giant with a native MCP server, after Google’s chrome-devtools-mcp. Safari Technology Preview 247 builds one right into the browser, and the pitch is simple: your coding agent can finally see how its code actually renders in a real browser.
What agents get
It’s a standard local MCP server — Claude Code, Codex, Gemini, any MCP client connects directly. Flip on “remote automation and external agents” in Safari’s Developer settings and the agent gets 15 tools against a live Safari window: read the DOM, inspect network requests down to headers and timing, take screenshots, run JavaScript, pull console output, click and type, emulate mobile viewports. Typical loop: point it at your dev server, let it spot the broken layout, fix the CSS, and verify — no human copy-pasting screenshots. Nice touch: it converts pages to Markdown using WebKit’s own pipeline, so agents get clean text instead of DOM soup.
Why it matters
Everything runs locally — no Apple cloud, no access to your history or AutoFill. But the real headline is Apple officially embracing MCP. With WebKit and Chromium both on board, agent-driven browser debugging just became table stakes. HN front page agrees: 100+ points in hours.
You Might Also Like
- Google Rolls out File Generation in Gemini Chasing Chatgpt Canvas and Claude Artifacts
- Googles Chrome Devtools mcp Crosses 29k Stars 29 Tools That Give ai Agents Eyes in the Browser
- Agent Kernel Gives any ai Coding Agent Persistent Memory With Just Three Markdown Files
- Proofshot Adds Visual Verification to ai Coding Agents no mcp Server Required
- Gemini Import Memory Tools Google Builds the Easiest off Ramp From Chatgpt yet
Top AI Product 
Leave a comment