| FMRS | 50 / 100 · D | 76 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 6 / 20 | 12 / 20 |
|---|
| Maintenance | 12 / 20 | 17 / 20 |
|---|
| Documentation | 13 / 20 | 17 / 20 |
|---|
| Setup experience | 11 / 20 | 17 / 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
| - Frontend developers who want AI-assisted web debugging and performance analysis
- Scenarios that need browser automation and performance diagnostics in the same tool
|
|---|
| 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
| - Cases that only need to scrape page text without performance analysis or complex interaction (a lighter scraping tool is a better fit)
|
|---|
| 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 a local Chrome browser instance to run
- navigate_page can visit any URL; type_text/fill_form and similar tools can enter arbitrary content into the page
|
|---|
| 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 tools can access and manipulate the content of open pages — use only in a trusted development/test environment
- performance_start_trace and similar tracing tools continuously record browser activity — avoid leaving them running on pages containing sensitive information
|
|---|
| Supported clients | Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Cline, Continue, Goose, LM Studio, Zed | Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Cline, Amp, Kiro, Antigravity |
|---|
| Tools | 97 | 22 |
|---|