MCP Safari Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | Navigate Safari to a specific URL |
| execute_scriptB | Execute JavaScript in the current Safari page |
| get_page_infoA | Get information about the current page (URL, title, etc.) |
| take_screenshotB | Take a screenshot of the current Safari window |
| get_console_logsB | Get console logs from the current page |
| refresh_pageA | Refresh the current Safari page |
| go_backA | Navigate back in Safari history |
| go_forwardA | Navigate forward in Safari history |
| start_error_monitoringC | Start monitoring Safari for JavaScript errors and optionally send them to Claude Code |
| stop_error_monitoringB | Stop monitoring Safari for JavaScript errors |
| click_elementC | Click on an element in the page using CSS selector |
| type_textB | Type text into an input element |
| scroll_toC | Scroll to a specific element or position |
| select_optionC | Select an option from a dropdown |
| get_element_textB | Get the text content of an element |
| wait_for_elementC | Wait for an element to appear on the page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose with no overlap: navigation tools (navigate, go_back, go_forward, refresh_page), element interaction tools (click_element, get_element_text, select_option, type_text, wait_for_element, scroll_to), page information tools (get_page_info, get_console_logs, take_screenshot), script execution (execute_script), and error monitoring (start_error_monitoring, stop_error_monitoring). The descriptions make it easy to differentiate between similar-sounding tools like get_element_text and get_page_info.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., click_element, execute_script, get_console_logs). The naming is predictable and readable throughout, with no deviations in style or convention. This consistency helps agents easily parse and understand the toolset.
With 16 tools, the count is well-scoped for a Safari automation server, covering essential browser interactions without bloat. Each tool serves a specific, useful function in web automation (e.g., navigation, element manipulation, debugging), and there are no redundant or trivial tools. This aligns with typical automation toolkits that require a moderate number of focused operations.
The toolset provides comprehensive coverage for Safari automation, including navigation (navigate, go_back, go_forward, refresh_page), element interaction (click, type, select, wait, scroll), page inspection (info, logs, screenshot), script execution, and error monitoring. There are no obvious gaps; agents can perform full web automation workflows from loading pages to interacting with elements and debugging, with clear lifecycle coverage (e.g., start/stop monitoring).