Introducing the Safari MCP server for web developers

1 min read
mcpai-agentsdeveloper-toolsbrowser-automation
View as Markdown
Originally from webkit.org
View source

My notes

Summary

Safari Technology Preview 247 ships a built-in MCP (Model Context Protocol) server that lets AI coding agents connect directly to a live Safari tab - reading the DOM, network requests, console output, and screenshots - instead of relying on a developer to manually copy-paste browser state into a prompt. It runs entirely locally, makes no network calls of its own, and exposes 16 tools covering navigation, JS evaluation, accessibility checks, and performance timing.

Key Insight

  • Closes the “debugging dance” loop. Normal workflow: see a bug, open devtools, inspect DOM/styles, screenshot it, describe it to an agent, wait, repeat. The MCP server lets the agent inspect the live page itself, cutting the window-hopping.
  • 16-tool surface, not just screenshots: browser_console_messages, browser_dialogs, create_tab/close_tab/list_tabs/switch_tab, evaluate_javascript, get_network_request, list_network_requests, get_page_content (markdown/HTML/JSON), navigate_to_url, page_info, page_interactions (click/type/scroll/hover/keyPress), screenshot, set_emulated_media, set_viewport_size, wait_for_navigation.
  • Cross-browser compat use case: agent opens the site in Safari specifically, inspects computed styles and layout, and diffs against what’s expected - useful because most dev/test workflows default to Chrome-only and silently miss Safari-specific bugs.
  • Goes beyond visual debugging: performance analysis (navigation timing, resource load times via evaluate_javascript) and accessibility auditing (missing labels, improper ARIA, poor contrast) are first-class use cases, not afterthoughts.
  • Privacy model stated explicitly by Apple/WebKit: runs entirely on the local machine, no network calls of its own, no access to AutoFill or other Safari browsing data. Captured page content/screenshots/console logs go straight to the connected agent, not to Apple - but from there it’s subject to whatever that agent/model does with it.
  • No special prompting required. Once registered, agents pick up the tool automatically on plain requests like “find bugs on my site in Safari” or “how accessible is my site in Safari” - no need to name the MCP server explicitly.