Screeny MCP Server: Privacy first macOS Screenshots for AI Agents
A privacy-first, macOS-only MCP server that enables AI agents to capture screenshots of pre-approved application windows, providing secure visual context for development and debugging tasks.
[!IMPORTANT] Requires Screen Capture permission + Window Approval Setup - see instructions below.
🔒 Privacy-First Design
Unlike other screenshot tools, Screeny requires explicit user approval for each window before it can be captured:
- Window approval system - Only pre-approved windows can be captured (approved during setup)
- User-controlled access - You decide exactly which windows are accessible
- Non-intrusive capture - Screenshots taken in background without changing window focus or interrupting your workflow
- No external connections - Screeny runs entirely on your device, screenshots are deleted immediately after use
Available Tools
-
listWindows- Lists all approved application windows available for screenshot capture.- Only shows user approved windows
-
takeScreenshot- Captures a screenshot of a specific window by its ID.- Captures windows in background - no need to bring window to front, but cannot capture minimized windows
- Provides actual pixel data - full-fidelity image, not OCR or text extraction
- JPEG compression with configurable cap - screenshots are always JPEG-compressed with a base64 payload cap (default preset: Medium / 250KB), configurable and clamped to 100–900KB
Resources
screeny://info- Server information and configuration details
Configuration
Claude Desktop
- Open Claude settings → Developer → Edit Config
- Add configuration
- Restart Claude Desktop after saving config
Using pipx
First install with: pipx install mcp-server-screeny
{
"mcpServers": {
"screeny": {
"command": "mcp-server-screeny",
"args": []
}
}
}
Note: If you get an
ENOENTerror, replace"mcp-server-screeny"with the full path to the executable (find it withwhich mcp-server-screenyin your terminal).
Using uvx
{
"mcpServers": {
"screeny": {
"command": "uvx",
"args": ["mcp-server-screeny"]
}
}
}
Note: If you get a "spawn uvx ENOENT" error, replace
"uvx"with the full path to uvx:which uvx # Find your uvx pathThen use that full path in the config (e.g.,
"/opt/homebrew/bin/uvx").
Cursor
- Open Cursor settings → Tools & Integrations → MCP Tools
- Add configuration
- Restart Cursor after saving config
Using pipx
First install with: pipx install mcp-server-screeny
{
"mcpServers": {
"screeny": {
"command": "mcp-server-screeny",
"args": []
}
}
}
Note: If you get an
ENOENTerror, replace"mcp-server-screeny"with the full path to the executable (find it withwhich mcp-server-screenyin your terminal).
Using uvx
{
"mcpServers": {
"screeny": {
"command": "uvx",
"args": ["mcp-server-screeny"]
}
}
}
Note: If you get a "spawn uvx ENOENT" error, replace
"uvx"with the full path to uvx:which uvx # Find your uvx pathThen use that full path in the config (e.g.,
"/opt/homebrew/bin/uvx").
[!NOTE] > Cursor MCP host
- Cursor auto context summarization can trigger looping tool calls (repeated screenshots).
- If this happens, lower the KB cap (use a smaller preset) or choose a model with a larger context window.
Setup
1. Grant Screen Capture Permission (Required)
Important: Grant permission before running window approval.
Note: You need to grant Screen Capture permission to BOTH:
- Your Terminal application (Terminal.app, iTerm2, etc.) - Required for running setup (can be disabled after)
- Your MCP host (Claude Desktop, Cursor) - Required for taking screenshots
To add them:
- Open System Settings > Privacy & Security > Screen & System Audio Recording
- Click the "+" button
- Add your Terminal application AND your MCP host application
- Restart both applications after granting permissions
2. Window Approval (Required)
After configuring your MCP client above, approve which windows can be captured.
If using pipx
# Interactive approval
mcp-server-screeny --setup
# Auto-approve all current windows
mcp-server-screeny --setup --allow-all
If using uvx
# Interactive approval
uvx mcp-server-screeny --setup
# Auto-approve all current windows
uvx mcp-server-screeny --setup --allow-all
Approvals are saved to ~/.screeny/approved_windows.json. Re-run setup when you want to update the list of approved windows.
Advanced Options (Optional)
During setup, you can configure the screenshot size preset (affects stability and clarity):
- Tiny (50KB) — most stable; fine text will blur
- Small (100KB) — recommended default; balanced clarity and stability
- Medium (250KB) — more detail; may be slower and heavier
- Large (500KB) — high detail; may trigger client summarization
- XL (750KB) — maximum detail; most error-prone
Your choice is saved in ~/.screeny/config.json as max_b64_kb. You can also override via the SCREENY_MAX_B64_KB environment variable. The active cap is clamped to 100–900KB.
Security & Privacy
- Only user-approved windows can be captured
- All processing stays local on your machine
- Screenshots are temporary and deleted immediately after use
Troubleshooting
Permission Issues
# Test window detection and permissions
mcp-server-screeny --debug
# Re-run setup if windows changed
mcp-server-screeny --setup
Common Issues
"spawn uvx ENOENT" error
- Solution: Use the full path to uvx in your MCP config instead of just
"uvx" - Find path with:
which uvx - Example:
"/opt/homebrew/bin/uvx"or"/usr/local/bin/uvx"
"No approved windows found"
- Solution: Run
mcp-server-screeny --setupfirst (oruvx mcp-server-screeny --setupif using uvx)
"Screen Recording permission required" or "No windows found"
- Solution: Grant Screen Recording permission in System Settings > Privacy & Security > Screen & System Audio Recording
- Click "+" button and manually add your MCP host (Claude Desktop, Cursor, etc.)
- Restart your MCP host application after granting permissions
- Try running setup again after granting permissions
Contributing
Pull requests are welcome! Feel free to contribute new ideas, bug fixes, or enhancements.
This is my first MCP project - if you encounter any bugs, please open an issue and I'll do my best to fix them!
Why I Built This
I created this tool to streamline my mobile development workflow. I was tired of manually taking screenshots repeatedly to describe UI issues. With Screeny, Cursor can directly capture screenshots of my iOS simulator and iterate on the design in a loop. I'm excited to see how others will use this!
Requirements
- Python 3.10+
- macOS
- Screen Capture permission
License
MIT License
Metadata
Release files for iflow-mcp_rohanrav_screeny 0.3.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| iflow_mcp_rohanrav_screeny-0.3.6.tar.gz | 944.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| iflow_mcp_rohanrav_screeny-0.3.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 959.6 kB
Release files / iflow_mcp_rohanrav_screeny-0.3.6.tar.gz
| Download URL | iflow_mcp_rohanrav_screeny-0.3.6.tar.gz |
|---|---|
| Size | 944.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a7185d19dd35449995948039041a15583275f576b213945b6422bc4c13fe46fc
|
|
BLAKE2b-256 checksum How to use checksums |
562343a17d83ad068063f5bc061420a3880582aeb550684e30c3c8d4c95b8ae3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_rohanrav_screeny-0.3.6-py3-none-any.whl
| Download URL | iflow_mcp_rohanrav_screeny-0.3.6-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a8dab4bc36ecbe85522a28b8207b9bc7024c6a54c350859f8823b513349f667
|
|
BLAKE2b-256 checksum How to use checksums |
83b25822c3e054513cc734c36a5dd4785eaa69c6e09f06efc65a42446113a83c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.27 {"installer":{"name":"uv","version":"0.9.27","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|