How to Use Safari 27 MCP Server With Claude & Codex
Wondering how to use Safari 27 MCP server with Claude Code, Codex or another AI agent? The quick version is just below — then I’ll walk through the exact settings, what your agent can actually do with a live Safari window, and the privacy details Apple baked in.
Short answer:
Safari 27.0 shipped on 17 September 2026 with an official, built-in MCP server, per the WebKit team’s release post.
Enable it via Safari > Settings > Developer > “Allow remote automation and external agents”.
It runs via /usr/bin/safaridriver with the –mcp flag, and connects to Claude, Codex or any agent through a standard mcp.json config.
Your agent gets DOM access, network requests, screenshots and console output from a real Safari window.
It runs entirely on your local machine and makes no network calls of its own.
What Is the Safari 27 MCP Server?
On 17 September 2026, Apple released Safari 27.0, and buried in the official WebKit release post is the feature that matters most for anyone building with AI agents: an official MCP (Model Context Protocol) server built into the browser.
In plain English: your coding agent can now drive and inspect a real Safari window. The WebKit team pitches it for letting an agent “see how your code renders in Safari”, “verify user states in forms, checkout flows, selections & more”, “compare computed styles and layout to results in other browsers”, “test for accessibility issues like missing labels, improper ARIA attributes”, and “analyze performance with navigation timing and resource load times”.
Under the hood it’s not magic — it runs via /usr/bin/safaridriver with the --mcp flag. Apple took safaridriver, the WebDriver binary that has existed for years, and taught it to speak MCP. That’s why it works with Claude, Codex, and any other agent that reads a standard mcp.json configuration, the same way tools like the ones in my Claude Code managed MCP servers guide do.
How to Use Safari 27 MCP Server: Step-by-Step Setup
Here’s the exact path, straight from the WebKit post:
Unlock the Developer settings. If you don’t see a Developer pane, open Safari’s settings, go to Advanced, and tick “Show features for web developers”.
Allow agent access. Go to Safari > Settings > Developer and check “Allow remote automation and external agents”.
Point your agent at it. Add the server to your agent’s mcp.json configuration — the server itself is /usr/bin/safaridriver run with the --mcp flag.
Test it. Ask your agent to open a page you’re working on and describe what it sees. If it can screenshot the page and read the console, you’re wired up.
🔥 Want this set up without the guesswork? Inside the AI Profit Boardroom we break down browser-connected agent workflows like this Safari MCP setup — wiring MCP servers into Claude Code the right way on live calls — 3,700+ members, four live calls per week, daily tutorials, done-for-you templates and a 30-day roadmap.
Once connected, the practical wins come fast. The server exposes DOM access, network requests, screenshots and console output — which turns “Claude, I think the checkout button is broken on Safari” from a guessing game into a two-minute loop: the agent loads the page, reads the console, inspects the DOM, screenshots the state, and fixes the actual bug.
The use cases the WebKit team highlights map neatly onto agency work:
Cross-browser layout checks — compare computed styles and layout in Safari against what you built in Chrome, without owning a drawer full of test devices.
Form and checkout verification — the agent walks the flow and verifies user states instead of you clicking through it for the tenth time.
Accessibility passes — missing labels and improper ARIA attributes get caught by the agent, which is also quietly an SEO win.
Performance analysis — navigation timing and resource load times, pulled from the browser that a big share of your mobile traffic actually uses.
If you’re already running agents against other services — like I showed with the Google Home MCP or Surfer’s MCP for SEO workflows — Safari slots into the same mental model: one more tool server in your agent’s toolbox, except this one is shipped and signed by Apple.
Privacy: It All Stays on Your Mac
This is the part Apple clearly sweated. Quoting the WebKit post directly: “The MCP server runs entirely on your local machine. It makes no network calls of its own. It does not have access to your personal information in Safari.” Captured data goes to the agent you’re running — not to Apple.
What your agent gets
What the server never does
DOM access on pages it drives
Make network calls of its own
Network request visibility
Read your personal Safari data
Screenshots of the window
Send anything to Apple
Console output and timing data
Run without you enabling it in settings
Sensible defaults, too: the whole thing is off until you explicitly enable it in the Developer pane. If you want help deciding which MCP servers belong in your stack — and which are a security liability — book a free SEO strategy session and I’ll go through your setup with you.
The Bottom Line on How to Use Safari 27 MCP Server
Setup is genuinely a two-minute job: tick two boxes in Safari’s settings, add safaridriver with the --mcp flag to your mcp.json, and your agent has a real browser. The significance is bigger than the setup: Apple shipping a first-party MCP server, on 17 September 2026, is the strongest signal yet that MCP has won as the standard way agents touch software.
If you build websites, test in Safari through your agent from now on. If you build agent workflows for clients, this just became part of your standard toolkit.
FAQ: how to use safari 27 mcp server
Is the Safari MCP server free?
Yes. It ships as part of Safari 27.0, which Apple released on 17 September 2026. There’s no separate download or licence — you just enable it in Safari’s Developer settings.
Which AI agents work with it?
The WebKit team names Claude and Codex directly, and says any other agent works via a standard mcp.json configuration, since it speaks the Model Context Protocol.
Does it send my browsing data to Apple?
No. Per the official WebKit blog: “The MCP server runs entirely on your local machine. It makes no network calls of its own. It does not have access to your personal information in Safari.”
What is it built on under the hood?
It runs via /usr/bin/safaridriver with the –mcp flag — Apple built the MCP server on top of safaridriver, the same WebDriver binary that has powered Safari automation for years.
Why can’t I see the Developer menu in Safari?
You need to switch it on first: go to Safari’s Advanced settings and tick “Show features for web developers”. The Developer pane then appears, where you can allow remote automation and external agents.
Is it safe to leave enabled?
It only runs locally and only feeds the agent you’re running. That said, an agent with browser access can see whatever the browser can see, so I’d enable it on a dev profile and toggle it off when you’re not actively using it.
Next steps: if you want help putting Safari’s MCP server and agent-driven browser testing to work in your business, join the AI Profit Boardroom — 3,700+ members, four live calls per week, daily tutorials and done-for-you templates — or book a free SEO strategy session and we’ll build your plan together.
About the author
Julian Goldie is an SEO agency owner with 10+ years in SEO, 394K+ YouTube subscribers, a 100% Upwork job-success score, 75K+ community members across his groups, and the author of a best-selling SEO book. For agency work, book a call for a custom quote.
