own-computer-use
Related Servers
Alternatives to own-computer-use
No user-submitted related servers found.
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 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.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that lets AI models operate a Windows PC through screenshots, mouse, keyboard, clipboard, window control, and UI Automation, with safeguards for user input and restricted applications.3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents human-like control over Windows via visual perception and simulated mouse and keyboard input, enabling automation of any application without APIs.33 npm6MIT
- AlicenseAqualityBmaintenanceEnables any AI agent to perceive and control a Windows desktop through live screen capture, OCR, and safety-gated mouse/keyboard actions via a local HTTP API and MCP.81610MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets multiple AI agents safely share a Windows desktop by coordinating exclusive access to the mouse, keyboard, screen, and windows, with human consent, takeover, and full activity logging.10 npmMIT
TDQS
Scored across 21 tools
Each tool has a clearly distinct role: input actions (click, type, key, scroll, drag), screen inspection (screenshot, zoom, read_screen), display management, and meta/system tools are well separated. The several capture-related tools are distinguished by scope (whole virtual screen vs one monitor vs region zoom vs display listing) and their descriptions make the intended usage explicit.
All tools use a consistent `computer_` prefix with snake_case names, and there is no mixing of camelCase or unrelated conventions. Some names are noun-like (`computer_screenshot`, `computer_clipboard`) rather than pure verb_noun, but the pattern is predictable throughout.
At 21 tools, the server is slightly above the typical well-scoped range, but most tools earn their place by covering distinct GUI automation concerns. A few meta/extras such as `computer_teach_step` feel less essential, but the overall count is reasonable for full computer-use coverage.
The surface covers the core GUI lifecycle well: screen capture, mouse/keyboard input, clipboard, application launch, window focus, OCR, batch actions, and safety/review checks. Minor gaps remain, such as no explicit window listing, minimize/close/resize operations, or standalone right-button hold/release, but agents can work around these in most cases.