Overview
- WebKit added a Safari Model Context Protocol server in Safari Technology Preview 247 that lets MCP‑compatible agents connect to a controlled Safari automation session to inspect and interact with pages.
- The server exposes roughly 17 tools such as get_page_content, browser_console_messages, list_network_requests, screenshot, and page_interactions for common debugging tasks.
- Apple says the MCP server runs entirely on the user’s Mac, makes no network calls of its own, and uses an isolated safaridriver WebDriver session that does not access AutoFill, existing logins, or other personal Safari data.
- Independent maintainers who build community tools confirmed the differences and said they will continue to offer alternatives that drive a user’s real, logged‑in Safari with broader capabilities while Apple’s build focuses on a reproducible clean‑room workflow.
- The release helps validate MCP as platform infrastructure and could improve agent debugging reliability, but developers should watch for a move of the --mcp option into stable Safari and for how agent providers handle captured page data.