agy_computer_use.mcp_server
Related Servers
Alternatives to agy_computer_use.mcp_server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable AI agents to control Windows desktops through UI Automation element trees, native screenshots, app launching, batched action sequences, smart waits, and safety gates using normalized coordinates.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients on Windows to control the local mouse, keyboard, and screen understanding via MCP stdio, allowing automated workflows like viewing the screen, locating elements, clicking, typing, and verifying results.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables automation of native Windows desktop applications through screen capture, mouse/keyboard control, and waiting for UI changes, exposing them as MCP tools.1-
- AlicenseNot gradedqualityBmaintenanceEnables MCP agents to drive Windows applications by targeting individual windows—clicking, typing, scrolling, dragging, and reading accessibility trees or screenshots—without stealing the user's focus, mouse, or keyboard. Runs entirely locally alongside the user, with per-app approval and no cloud account or usage limits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to control Windows desktop applications through UI Automation and Win32, supporting window management, mouse/keyboard input, element inspection, screenshots, OCR, macro recording, and autonomous multi-app missions. It also provides an HTTP/stdio MCP interface, an operator UI, and optional telemetry and safety controls.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Windows desktop automation through a unified 29-tool MCP surface combining UI Automation, OCR, browser DOM reading, screenshots, window management, mouse/keyboard control, app launching, and notifications while intercepting dangerous calls.2MIT
TDQS
Scored across 12 tools
Tools target mostly distinct capabilities: capture, foreground input, background dispatch, visual anchoring, macro replay, and audit/verification. The main overlap is between foreground action tools (cu_click, cu_type, cu_hotkey, cu_scroll) and cu_bg_dispatch, but the focusless PostMessage distinction is explicit; cu_merkle_audit and cu_verify_oracle are also closely related but separable.
All names use the consistent cu_ prefix and snake_case, with predictable action-oriented names. Minor noun-like labels such as cu_hotkey do not break the overall pattern.
Twelve tools is well-scoped for a Windows computer-use server. Each tool covers a distinct capability layer such as capture, input dispatch, verification, background execution, or replay.
Core computer-use operations are covered: screen capture, UIA/SOM extraction, clicking, typing, hotkeys, scrolling, background capture/dispatch, template matching, macro replay, and audit receipts. Gaps include no explicit window enumeration/focus management, clipboard operations, or macro recording, but most can be worked around.