Safari introduces MCP server for local testing

The WebKit team has shipped the Safari MCP server, a lightweight local HTTP server that plugs directly into Safari’s devtools. Launched on macOS, the server runs from the command line, serves files from a developer‑specified directory, and automatically reloads pages as source files change. By exposing a standard http://localhost endpoint, it eliminates the need for third‑party servers or manual proxy configuration when testing web applications in Safari [WebKit Blog].

What shipped

• A binary (safari-mcp) that can be started with a single command, e.g. safari-mcp --root ./my‑site.
• Automatic HTTPS support via a self‑signed certificate, enabling developers to test secure contexts without extra setup.
• Integration with Safari’s Web Inspector, so breakpoints, network logs, and console output are tied to the live server instance.
• Support for HTTP/2 and HTTP/1.1, giving developers a realistic view of how their apps will behave in production.

Why it matters

The server streamlines the feedback loop: changes to HTML, CSS, or JavaScript are reflected instantly in Safari, cutting the time spent swapping between editors, terminals, and browsers. Because the server is bundled with WebKit, developers get a consistent environment that mirrors Safari’s runtime, reducing discrepancies that often arise when using generic local servers. The built‑in HTTPS capability also lets teams verify mixed‑content warnings and service‑worker behavior without configuring external certificates.

Getting started

Install the tool via Homebrew (brew install safari-mcp) or download the binary from the WebKit releases page. Once installed, run safari-mcp --root <folder> and open http://localhost:8000 in Safari. The Web Inspector will automatically detect the MCP session, exposing a “MCP” tab that shows active connections and live‑reload status. Documentation and sample projects are available on the WebKit blog page linked above.