Safari MCP Server
Related Servers
Alternatives to Safari MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceNative macOS browser (SwiftUI + WKWebView) that exposes an MCP server in-process so AI agents can drive a real local browser with the user's existing logged-in sessions. ~40 tools (navigate, click, fill, screenshot, eval_js, network log, accessibility tree). Local-only with bearer-token auth.1MIT
- AlicenseBqualityDmaintenanceProvides AI assistants with Safari browser automation and developer tools access, enabling LLMs to control Safari, access console logs, monitor network activity, and perform browser automation tasks.139 npm33MIT

BAP MCPofficial
AlicenseNot gradedqualityCmaintenanceLightweight browser automation server for AI agents, enabling fast (10-25ms per action), structured observations and semantic selectors with zero token overhead.6Apache 2.0- AlicenseAqualityDmaintenanceSafari Web Extension + Node.js MCP bridge giving Claude Desktop full control over Safari — navigate, read pages, click elements, fill forms, and manage tabs. No Playwright or WebDriver dependency.131MIT
- AlicenseNot gradedqualityDmaintenanceProvides native macOS desktop automation for AI agents, enabling screen capture, mouse/keyboard control, window management, and iOS/Android simulator control in both foreground and background modes without focus stealing.3MIT
- AlicenseNot gradedqualityAmaintenanceBrowser automation for AI agents: tabs, cookies, arbitrary JS execution (via CDP, bypasses CSP), screenshots, downloads, proxy switching, data cleanup. Chrome & Edge multi-browser, full permissions, zero configuration. 25+ MCP tools.1MIT
TDQS
Scored across 98 tools
Many tools occupy overlapping territory: reading page state is split across read_page, snapshot, accessibility_snapshot, analyze_page, get_source, and five extract_* tools, and interaction is fragmented into click/click_and_read/click_and_wait/native_click plus multiple fill/type variants. The descriptions try to differentiate them, but with this many near-neighbor tools an agent is likely to misselect.
All tools share a safari_ prefix and snake_case naming, and most follow verb_noun (navigate, read_page, set_cookie, throttle_network). Minor inconsistencies like noun-only names (local_storage, session_storage, network, css_coverage, doctor) and mixed clear/delete/reset verbs keep it from being fully consistent.
98 tools is far beyond the 50+ threshold for an extreme count mismatch. Even for broad Safari automation, the surface is bloated with micro-variants that could be consolidated (e.g. click, click_and_read, click_and_wait, native_click), and the volume will overwhelm agent context and tool-selection.
The domain of Safari browser automation is covered extensively: navigation, tab management, reading/interaction, forms, storage, network, console, device emulation, performance, and auditing. Only minor gaps exist (e.g. no dedicated download handling, no header-level user-agent emulation), which agents can generally work around.