How do I install the Safari MCP server?

Safari MCP ships inside Safari Technology Preview 247. Enable developer features and remote automation in Safari Settings, then run `claude mcp add safari-mcp-stp -- "/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver" --mcp` (swap `claude` for `codex` or another MCP client). No separate download.

Which tools does the Safari MCP server expose?

Safari MCP exposes 17 tools including screenshot, evaluate_javascript, navigate_to_url, get_page_content, page_interactions (click/type/scroll), list_network_requests, browser_console_messages, set_viewport_size and set_emulated_media — the same primitives a developer uses in Web Inspector, wrapped as MCP calls.

Does Safari MCP send my data to Apple?

No. Safari MCP runs locally through safaridriver and makes no network calls of its own. Page content, screenshots and console output go straight to the connected agent, and the server has no access to AutoFill or personal Safari data — everything stays on the user's Mac.

How is Safari MCP different from Playwright or Puppeteer?

Playwright and Puppeteer are code libraries a developer imports into a script. Safari MCP is an agent-facing protocol: an LLM can call the 17 tools directly through MCP without generating browser-automation code. It also drives the real Safari engine (not Chromium), so agents can test compatibility on Apple's stack.

Apple WebKit · 2026-07-01 · major

Safari MCP server — Apple lets AI agents drive Safari to debug websites

Apple's Safari Technology Preview 247 ships an MCP server that gives coding agents 17 tools to inspect the DOM, capture screenshots, evaluate JavaScript, and drive a live Safari window. Runs locally, no data leaves the device.

WebKit blog preview card announcing the Safari MCP server

Apple gives coding agents a direct line into Safari — 17 MCP tools for the DOM, network, console, screenshots and clicks.

Quick facts

Maker	Apple (WebKit)
Requires	Safari Technology Preview 247
Tools	17
Runs	Locally, no cloud
Compatible with	Any MCP client (Claude Code, Codex, etc.)
Price	Free

What is it?

Safari MCP is an MCP server bundled with Safari Technology Preview 247 that lets AI coding agents connect to a live Safari window. The server exposes 17 tools — screenshots, DOM reads, JavaScript evaluation, network inspection, page navigation and typing/clicking — through the Model Context Protocol, the open standard Anthropic contributed to the Linux Foundation.

How does it work?

The MCP server runs locally on top of `safaridriver`, the same automation binary Safari has shipped for years. An MCP client such as Claude Code or Codex spawns safaridriver with the `--mcp` flag; the agent then calls JSON-RPC tools like `screenshot`, `evaluate_javascript`, `page_interactions` and `list_network_requests`. All page data goes to the agent, not to Apple.

Why does it matter?

Before Safari MCP, coding agents on macOS had to shell out to Chromium via Playwright or Puppeteer to test a change in a browser. Safari MCP puts the real Safari engine — the one Apple users actually load websites in — under agent control, so an agent can catch compatibility bugs, layout regressions and accessibility issues on WebKit without a human clicking around.

Who is it for?

web developers using Claude Code, Codex or other MCP-aware coding agents on macOS

Frequently asked questions

How do I install the Safari MCP server?: Safari MCP ships inside Safari Technology Preview 247. Enable developer features and remote automation in Safari Settings, then run `claude mcp add safari-mcp-stp -- "/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver" --mcp` (swap `claude` for `codex` or another MCP client). No separate download.
Which tools does the Safari MCP server expose?: Safari MCP exposes 17 tools including screenshot, evaluate_javascript, navigate_to_url, get_page_content, page_interactions (click/type/scroll), list_network_requests, browser_console_messages, set_viewport_size and set_emulated_media — the same primitives a developer uses in Web Inspector, wrapped as MCP calls.
Does Safari MCP send my data to Apple?: No. Safari MCP runs locally through safaridriver and makes no network calls of its own. Page content, screenshots and console output go straight to the connected agent, and the server has no access to AutoFill or personal Safari data — everything stays on the user's Mac.
How is Safari MCP different from Playwright or Puppeteer?: Playwright and Puppeteer are code libraries a developer imports into a script. Safari MCP is an agent-facing protocol: an LLM can call the 17 tools directly through MCP without generating browser-automation code. It also drives the real Safari engine (not Chromium), so agents can test compatibility on Apple's stack.

Try it

claude mcp add safari-mcp-stp -- "/Applications/Safari Technology Preview.app/Contents/MacOS/safaridriver" --mcp