Safari Screenshot MCP Server
The Safari Screenshot MCP Server allows you to capture high-quality screenshots of webpages using Safari on macOS with various configurable options:
Capture Screenshots: Take screenshots of any webpage by specifying the URL
Custom Dimensions: Define width and height (default: 1024x768) or use device presets (iPhone, iPad, desktop)
Zoom Control: Adjust the zoom level (e.g., 0.5x, 1x, 2x, 50% zoom)
Wait Timing: Set a wait time before capturing to ensure the page is fully loaded (default: 3 seconds)
Custom Output: Specify where to save the screenshot (default:
./screenshots/[hostname]-[timestamp].png)Native Quality: Leverage Safari and macOS native tools for pixel-perfect captures
MCP Integration: Use with Cursor for command-based screenshot workflows
Auto-Cleanup: Automatically closes Safari windows after capturing
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Safari Screenshot MCP Server capture apple.com on iPhone 12 Pro with 2 second wait"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Safari Screenshot
A Node.js MCP Server for capturing screenshots using Safari on macOS.
Features
Capture window screenshots at specific sizes
Support for different zoom levels
Configurable wait times for page load
Clean up after capture
Native macOS screenshot quality
Related MCP server: Website Screenshot MCP
Usage
import { takeScreenshot } from './screenshot.js';
// Basic window screenshot
await takeScreenshot({
url: 'https://www.apple.com',
outputPath: './screenshot.png',
width: 1024, // Optional: window width (default: 1024)
height: 768, // Optional: window height (default: 768)
waitTime: 3, // Optional: seconds to wait for load (default: 3)
zoomLevel: 1, // Optional: page zoom level (default: 1)
});
// Responsive design testing
await takeScreenshot({
url: 'https://www.apple.com',
outputPath: './mobile.png',
width: 375, // iPhone SE width
height: 667, // iPhone SE height
zoomLevel: 1,
});
// High-resolution capture
await takeScreenshot({
url: 'https://www.apple.com',
outputPath: './desktop-hd.png',
width: 1920, // Full HD width
height: 1080, // Full HD height
waitTime: 5, // Wait longer for HD content
zoomLevel: 0.8, // Zoom out slightly
});Requirements
macOS
Safari
Node.js >= 14.0.0
Terminal needs Accessibility permissions (System Preferences → Security & Privacy → Privacy → Accessibility)
Installation
npm install safari-screenshotOptions
Option | Type | Default | Description |
url | string | required | The URL to capture |
outputPath | string | auto | Where to save the screenshot (default: ./screenshots/[hostname]-[timestamp].png) |
width | number | 1024 | Window width in pixels |
height | number | 768 | Window height in pixels |
waitTime | number | 3 | Seconds to wait for page load |
zoomLevel | number | 1 | Page zoom level (1 = 100%) |
Common Viewport Sizes
The module is tested with these common viewport sizes:
Desktop: 1920×1080 (Full HD)
Laptop: 1366×768
Tablet Landscape: 1024×768
Tablet Portrait: 768×1024
Mobile Large: 428×926 (iPhone 12 Pro Max)
Mobile Medium: 390×844 (iPhone 12 Pro)
Mobile Small: 375×667 (iPhone SE)
How It Works
Opens Safari with specified window size
Loads the URL and waits for page load
Applies zoom level if specified
Uses native macOS screencapture for pixel-perfect results
Verifies screenshot was captured successfully
Cleans up Safari windows
Permissions
This package requires System Events permissions to work:
Open System Preferences > Security & Privacy > Privacy > Accessibility
Add Terminal (or your IDE) to the list of allowed apps
Using with Cursor
Setup in Cursor
Open Cursor
Go to settings, "Add MCP Server"
In the configuration dialog:
Name:
safari-screenshotType:
commandCommand:
npx -y @rogerheykoop/mcp-safari-screenshot
Or for local development:
Command:
npx -y /path/to/mcp-safari-screenshot/server.js
Example Commands
After connecting to the server in Cursor, you can use these commands:
Take a screenshot of https://apple.com at desktop sizeResponse: Will capture at 1920×1080
Capture https://apple.com on iPhone 12 ProResponse: Will capture at 390×844
Screenshot github.com at 50% zoomResponse: Will capture with zoomLevel: 0.5
Supported Parameters
The MCP server understands these concepts:
Device names (e.g., "iPhone", "iPad", "desktop")
Dimensions (e.g., "1024x768")
Zoom levels (e.g., "50% zoom", "2x zoom")
Wait times (e.g., "wait 5 seconds")
Example Workflows
Responsive Testing
Take screenshots of apple.com on iPhone, iPad, and desktopZoom Testing
Capture github.com at 75% zoom and 125% zoomCustom Size
Screenshot example.com at 1440x900
Tips
Screenshots are saved to the
screenshotsdirectory by defaultDevice names automatically set appropriate dimensions
The server handles cleanup of Safari windows
Use "wait X seconds" for slow-loading pages
Troubleshooting
If you encounter issues:
Check Terminal has Accessibility permissions
Verify Safari is not in private browsing mode
Ensure the working directory is writable
Check Cursor's console for error messages
License
MIT
Testing Locally
You can test the MCP implementation directly:
# Test discovery
echo '{"type":"discover"}' | npx -y ./server.js
# Test screenshot
echo '{"type":"execute","tool":"take_screenshot","input":"Take a screenshot of https://apple.com","requestId":"123"}' | npx -y ./server.jsExpected responses:
Discover will return capabilities
Execute will:
Log progress to stderr
Return result JSON to stdout
Save screenshot to ./screenshots/
Available Tools
1 tooltake_screenshotC
Take a screenshot of a webpage using Safari on macOS
Inputs: url (required), outputPath, width, height, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is singular and clearly defined, making it impossible for an agent to misselect between non-existent alternatives.
A single tool inherently has perfect naming consistency as there are no other tools to compare against. The name 'take_screenshot' follows a clear verb_noun pattern, which would be consistent if more tools existed.
One tool is too few for most server purposes, as it severely limits functionality and scope. While it matches the server's name, a single screenshot tool feels thin and incomplete for a broader screenshot or browser automation domain.
The tool surface is severely incomplete for a screenshot server. There are obvious gaps such as no options for different screenshot types (e.g., full-page, element-specific), no configuration settings, and no related operations like listing or managing screenshots.
Maintenance
Related MCP Connectors
Capture website screenshots (viewport or full page) with local Chrome, or on OpenScreenShot Cloud.
Pixel-perfect webpage screenshots rendered in a real browser, full-page or viewport, via one POST.
Full-page, first-screen, mobile or element screenshots of any URL as PNG, JPEG or PDF.
Screenshot any website as PNG, JPEG, WebP, PDF or scrolling MP4/GIF video, with public file links.
Related MCP Servers
- -licenseAqualityNot gradedmaintenanceA server that provides AI assistants programmatic control of Safari browser on macOS for web automation, testing, and debugging.161-
- AlicenseCqualityDmaintenanceA server that allows AI agents and clients to programmatically capture screenshots of websites with options for image format and viewport selection.121 npm9MIT
- AlicenseNot gradedqualityDmaintenanceCaptures full-monitor screenshots and returns them as base64 inline or saved file. Supports macOS, Linux, Windows, and WSL2.21 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides tools to capture pixel-perfect website screenshots as images or PDF. Supports configurable viewport, full-page capture, CSS injection, and returns either viewable images or base64-encoded content.MIT