A **privacy-first, macOS-only MCP server** that enables AI agents to capture screenshots of pre-approved application windows, providing secure visual
Screeny MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 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.
Once Screeny is connected, these are the calls the assistant has available:
listWindows — Lists all approved application windows available for screenshot capturetakeScreenshot — Captures a screenshot of a specific window by its IDResources — The Resources tool exposed by this serverCursor — 1. Open Cursor settings → Tools & Integrations → MCP Tools 2. Add configuration 3. Restart Cursor after saving configENOENT on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the browser automation options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Screeny's toolset — listWindows, takeScreenshot, Resources and 1 more — is a fair guide to whether it matches your workflow. It is maintained by rohanrav; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| listWindows | Lists all approved application windows available for screenshot capture. |
| takeScreenshot | Captures a screenshot of a specific window by its ID. |
| Resources | The Resources tool exposed by this server. |
| Cursor | 1. Open Cursor settings → Tools & Integrations → MCP Tools 2. Add configuration 3. **Restart Cursor** after saving config |
{
"mcpServers": {
"screeny": {
"command": "mcp-server-screeny",
"args": []
}
}
}Configuration as documented by the project. Restart the client after saving.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.