Screen Control runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 29 Oct 2026.
Safety-gated computer use for AI agents: screen OCR and vision, mouse, keyboard, window control.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
p = subprocess.Popen([exe])
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Screen Control
same job, measured the same wayMCP server for browser and desktop automation: OCR, image recognition, real mouse and keyboard input
Vision tools for coding agents: screenshots, OCR, UI diffs, errors, tables, and charts.
Windows screenshots, OCR, and redacted screen recording for AI agents. No desktop app needed.
Local OCR & screen understanding for agents: read any window, find what to click. No uploads.
Screen observation, OCR and permission-controlled app input over MCP for Apple silicon Macs.
Plonk gives agents local macOS tools for windows, workspaces, screenshots, OCR, and more.
Web extraction, OCR (Japanese-strong), invoice and company data for AI agents. x402, no API key.
Secure Linux desktop automation - input, screen/OCR/vision, AT-SPI2 UI tree, window, clipboard
Screen Control — questions
Answers built from our own checks of this server.