Safari DevTools MCP
Let your coding agent drive Safari DevTools for live debugging, DOM inspection, and browser automation on macOS without leaving the editor.
Overview
Safari DevTools MCP is a MCP server for the Build phase that connects AI coding agents to Safari DevTools for browser debugging and automation on macOS.
What is this MCP server?
- stdio MCP server (npm package safari-devtools-mcp v1.8.1) via npx for Claude Code and compatible agents
- Connects AI agents to Safari DevTools for debugging and automation, not generic headless Chrome-only flows
- Targets macOS Safari workflows where cross-browser parity matters for indie web and extension builders
- Repository: github.com/HayoDev/safari-devtools-mcp with MCP schema 2025-12-11
- Published server version 1.8.1 on npm (identifier safari-devtools-mcp)
- Transport: stdio; runtime hint npx
- MCP server schema: 2025-12-11
What problem does it solve?
Agents can edit frontend code but often cannot see or control Safari, so WebKit-only bugs stay invisible until manual QA.
Who is it for?
Indie builders on macOS who ship web or hybrid products and want agent-driven Safari debugging without maintaining a custom DevTools bridge.
Skip if: Teams that only test in Chromium, build pure CLI/backend services with no browser surface, or need Linux/Windows-native browser MCP.
What do I get? / Deliverables
After you register the server, your agent can use Safari DevTools-backed debugging and automation while you iterate on web UI in the build loop.
- Registered stdio MCP server pointing at safari-devtools-mcp
- Agent-accessible Safari DevTools debugging and automation session
- Faster iteration on Safari-specific frontend issues during build
Recommended MCP Servers
Journey fit
Browser-facing fixes and UI verification happen while you are building the product, before formal ship-phase QA gates. Frontend and web UI work is where Safari-specific behavior, WebKit quirks, and client-side bugs surface and need agent-assisted DevTools access.
How it compares
Safari-specific browser MCP integration, not a full test runner or a generic Playwright skill.
Common Questions / FAQ
Who is Safari DevTools MCP for?
It is for solo builders and small teams using Claude Code, Cursor, or similar agents who develop on macOS and need Safari/WebKit debugging in the agent workflow.
When should I use Safari DevTools MCP?
Use it during frontend build and fix cycles when UI bugs appear only in Safari, or when you want the agent to inspect and automate a page in Safari DevTools.
How do I add Safari DevTools MCP to my agent?
Add an MCP stdio entry that runs npx safari-devtools-mcp (v1.8.1 from npm), restart the agent, and ensure Safari and Web Inspector are available on your Mac.