Screen Control
Related Servers
Alternatives to Screen Control
- AlicenseNot gradedqualityBmaintenanceMCP server that enables Claude to control your computer, similar to Anthropic's computer use but easy to set up locally.3,776 npm405MIT
- AlicenseNot gradedqualityCmaintenanceLocal MCP server for Gateway-managed computer use that exposes computer.* tools with desktop control, OCR, and user-visible safety overlays.1MIT
Related Servers
- FlicenseNot gradedqualityDmaintenanceA local, dependency-free MCP server that gives AI agents controlled access to the active Windows desktop, enabling automated interaction with applications through screenshots, clicks, typing, and window management.1-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to see and operate a Windows PC through mouse, keyboard, screenshots, OCR, window control, and shell commands.-
- AlicenseAqualityCmaintenanceAllows AI clients to see and control Windows 10/11 desktops via MCP, with screenshots, UI Automation, Chrome CDP, keyboard/mouse, and terminal using semantic element targeting.30MIT
- AlicenseAqualityDmaintenanceEnables LLM agents to capture screenshots, control mouse/keyboard, and manage windows on desktop platforms, primarily Windows, via an MCP server.161MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to control a Windows PC via MCP, including launching apps, managing windows, driving keyboard and mouse, reading the screen with OCR, and monitoring system state, with multi-agent locking and a local dashboard for confirmation.MIT
- FlicenseNot gradedqualityCmaintenanceA local MCP server that enables AI agents to inspect and control a Windows machine through permission-gated tools for system information, windows, UI elements, files, applications, screenshots, input, and multi-step workflows.-
TDQS
Scored across 16 tools
Each tool targets a distinct mechanism—screen capture, OCR, motion detection, global input, window-specific input, window introspection, and game mode. Potentially similar tools like ocr_screen and window_capture_ocr are cleanly separated by foreground screen versus background window. No two tools appear to do the same job.
Most tools follow a readable snake_case convention with verb-first names like list_windows, focus_window, close_window, and release_all. A few noun-style names like mouse, keyboard, and game, plus window_post and window_capture_ocr, are minor deviations but still clear and predictable.
Sixteen tools is on the higher end but each earns its place across capture, OCR, input, window management, and game mode. The count feels slightly heavy but remains well-scoped for a desktop automation server.
Core workflows are well covered: screen capture, OCR, change detection, global and background input, window discovery, focusing, posting, and closing. Minor gaps like querying the current cursor position or window geometry are absent but most operations have workarounds.