| FMRS | 50 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 10 / 20 |
|---|
| Security and permissions | 6 / 20 | 14 / 20 |
|---|
| Maintenance | 12 / 20 | 15 / 20 |
|---|
| Documentation | 13 / 20 | 15 / 20 |
|---|
| Setup experience | 11 / 20 | 12 / 20 |
|---|
| Best for | - AI coding agents running on macOS with Safari
- Automation that must reuse real Safari logins, cookies, and sessions
- Users who want background browser operation with lower additional CPU usage
- Developers validating Safari, WebKit, or iOS pages
| - Developers who want AI clients to directly control the browser
- Scenarios requiring DOM-level understanding and low-latency automation (50-200 ms)
- Multi-client support (Claude Code, Cursor, VS Code, etc.)
- Internal tools or automation scripts needing browser interaction
|
|---|
| Not for | - Non-macOS environments
- Tasks requiring Chrome-specific debugging, Lighthouse, or performance tracing
- Clean, isolated WebDriver sessions without the user's browser state
- Users unwilling to grant Safari automation, screen-recording, or accessibility permissions
| - Headless browser or server-side monitoring
- Bypassing website restrictions or unsupervised automation
- Automation on sensitive pages without human supervision
- Complex scenarios that require visual understanding (e.g., screenshots)
|
|---|
| Required permissions | - Safari: Allow JavaScript from Apple Events
- macOS Automation access to Safari for the parent app running the MCP server
- Screen Recording for screenshots
- Accessibility for safari_native_* tools and safari_save_pdf
| - Requires installing the Chrome extension, which requests permissions for active tab, debugger, storage, etc.
- MCP server needs to connect to the extension via WebSocket (default ws://localhost:7225)
- Optional Streamable HTTP mode requires allowing connections to http://127.0.0.1:7226/mcp
- Uploading files requires providing absolute local paths
|
|---|
| Risks and side effects | - The tools can operate the real logged-in Safari and may access accounts, cookies, clipboard contents, and page data
- safari_evaluate and related script tools can execute arbitrary JavaScript in the current page
- Exported or imported storage may contain session information
- Native input tools can produce real click, keyboard, and hover events in a non-frontmost Safari window
- Automation of financial, social, or other sensitive sites should be reviewed before execution
| - Browser automation can be unpredictable on complex or sensitive sites; supervision is required
- Credentials and payment info are stored in a vault but require user unlock flows
- API keys are encrypted in Chrome storage, but clients may send page context to model providers
- MCP server is a local process, posing local security risks
- Capability catalog allows most non-denied origins but is gated by multiple checks
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Cline, Continue, Goose, LM Studio, Zed | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Codex |
|---|
| Tools | 97 | 30 |
|---|