Safari MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAFARI_PAGE_TIMEOUT | No | Page load and selector wait timeout, in milliseconds. | 10000 |
| SAFARI_WINDOW_WIDTH | No | Browser window width, in pixels. | 1280 |
| SAFARI_WINDOW_BOUNDS | No | Browser window margin offset from top-left corner, in pixels. | 20 |
| SAFARI_WINDOW_HEIGHT | No | Browser window height, in pixels. | 1024 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clickC | Click an element on the browser window |
| closeA | Close the working tab |
| executeA | Execute JavaScript in the browser context |
| hoverA | Hover over an element to reveal hover-triggered UI |
| inspectA | Inspect a page element by CSS selector |
| navigateA | Navigate to a URL or through browser history (back/forward) |
| openA | Open a blank tab as the working target |
| readA | Get the page title, URL, and either text content or anchor links |
| refreshB | Refresh the current browser page |
| screenshotA | Capture a screenshot of the browser window, an element, the full page, or the screen |
| scrollA | Scroll to specific viewport page or by direction with pixel amount |
| searchA | Search the web using browser's default search engine |
| selectA | Choose an option in a element |
| statusA | Get the current Safari tabs and the full tool surface with usage guidance |
| typeB | Type text into a page input field |
| waitA | Wait for a selector to appear, disappear, or text to appear |
| windowC | Manage browser window tabs |
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 17 tools
Each tool has a clearly distinct purpose: click, hover, select, type, scroll are all different interactions; navigate, open, close, refresh, window manage tabs/navigation; read, inspect, screenshot extract data; execute runs JS; wait adds synchronization. No overlapping tools.
All tool names are single lowercase words, predominantly verbs (click, navigate, type) with 'screenshot' as a slight exception but still consistent in style. No mixing of conventions.
17 tools is slightly above the ideal range of 3-15, but the set covers a wide range of browser actions without feeling bloated. Each tool serves a distinct need in web automation.
The tool set covers navigation, element interaction, information retrieval, execution, and basic synchronization. Missing advanced features like file upload or alert handling, but core workflows for browsing and testing are well-supported.