Screenshot MCP (macOS)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCREENSHOT_MCP_BIN | No | Path to the compiled Swift binary | |
| SCREENSHOT_MCP_OUTPUT_DIR | No | Default output directory for screenshots |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_displaysB | List available displays with bounds and pixel sizes. |
| list_windowsB | List on-screen windows with bounds and owner metadata. |
| screenshot_displayC | Capture a PNG/JPG of a display by display_id. |
| screenshot_windowC | Capture a PNG/JPG of a window by window_id. |
| record_window_durationC | Record a window for a fixed duration (seconds) to an MP4. fps defaults to 10. system_audio records global system audio. |
| record_window_startB | Start recording a window until record_window_stop is called. fps defaults to 10. system_audio records global system audio. |
| record_window_stopB | Stop a recording started with record_window_start. |
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 7 tools
Each tool has a clearly distinct purpose: listing displays vs. windows, recording windows with duration vs. start/stop control, and screenshotting displays vs. windows. The descriptions make it easy to differentiate between similar tools like record_window_duration and record_window_start, as one specifies a fixed duration while the other allows manual control.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., list_displays, record_window_duration, screenshot_display). The naming is predictable and readable throughout the set, making it easy for agents to understand the action and target.
With 7 tools, the server is well-scoped for screenshot and recording functionality on macOS. Each tool earns its place by covering essential operations: listing resources, recording windows with different control methods, and capturing screenshots of displays and windows, without unnecessary bloat.
The tool surface provides complete coverage for the domain of macOS screen capture and recording. It includes listing (displays and windows), recording (with both fixed-duration and start/stop control), and screenshotting (displays and windows), ensuring agents can handle all core workflows without dead ends.