MCP Safari Server
Related Servers
Alternatives to MCP Safari Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceLets your coding agent control and inspect a live Safari browser on macOS. Provides access to Safari DevTools for debugging, automation, and testing.4928 npm2MIT
- -licenseAqualityNot gradedmaintenanceA server that provides AI assistants programmatic control of Safari browser on macOS for web automation, testing, and debugging.161-
- 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
- AlicenseAqualityBmaintenanceEnables local macOS automation via the Model Context Protocol, allowing file operations, system monitoring, shell commands, clipboard access, and screenshots with configurable security restrictions.14MIT
- AlicenseAqualityAmaintenanceEnables browser automation through the Model Context Protocol, allowing AI agents to control Chrome, Firefox, or Edge for tasks like navigation, clicking, typing, and screenshots.4140 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables browser automation via the Model Context Protocol, supporting headless Playwright and extension bridges for controlling existing Chrome and Firefox tabs.4,799 npm-
TDQS
Scored across 16 tools
Each tool targets a distinct action (navigation, interaction, inspection, monitoring). There is no overlap; for example, click_element, type_text, and select_option are clearly different operations.
All tools follow a consistent verb_noun pattern in snake_case (e.g., click_element, get_page_info, start_error_monitoring). Even directional commands like go_back adhere to the convention.
16 tools is well-scoped for a Safari browser automation server. It provides sufficient functionality without being overwhelming.
The tool set covers essential browser operations: navigation, element interaction, page information, screenshots, script execution, console logs, and error monitoring. Minor gaps exist (e.g., no alert handling or window resizing), but core workflows are well-supported.