UI-Venus MCP
Related Servers
Alternatives to UI-Venus MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to see, locate UI elements, and operate any Windows desktop app through natural language, using accessibility-tree matching with optional vision-model fallback, plus an autonomous visual loop with introspection and meta-learning.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to automate real desktop applications across Windows, Linux, and macOS using incremental screen perception, accessibility trees, OCR, and window management, dramatically reducing token usage compared to screenshot-per-step approaches.34 PyPI4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to operate local desktops and Chromium browsers through MCP tools, unifying accessibility trees, physical input, screenshots, DOM/ARIA, visual grounding, and result verification.313 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to automate desktop operating systems and applications through UI automation, screenshots, and input simulation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely and truthfully control local desktop applications via native accessibility trees, supporting element inspection and automation without proprietary binaries or fake success responses.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to observe and operate a real Windows or Linux desktop like a human — snapshotting screen geometry, active window, OCR text and normalized UI elements, then clicking, typing, scrolling and managing windows with built-in verification and recovery. Backends are chosen automatically per action (UIA/AT-SPI → OCR → vision → PyAutoGUI), so browsers, IDEs, office suites and canvas apps are all controllable without any browser-automation MCP.MIT
TDQS
Scored across 17 tools
Most tools have clearly distinct scopes (single action vs. one autonomous step vs. full task delegation; different observation depths; recording vs. script execution). Some boundaries among computer_action, computer_step, computer_execute_task, and computer_run_script could blur, but descriptions and parameter differences largely disambiguate them.
All tool names use consistent computer_ snake_case with clear verb/noun or record_* patterns. There is no mixed casing or conflicting verb style.
17 tools is slightly above the typical 3-15 sweet spot, but the breadth of GUI automation capabilities (targets, observation, action, tasks, recording, scripting, testing) justifies most tools. A few tools could potentially be consolidated but are reasonable for this domain.
The surface covers target discovery, observation, element location, action execution, autonomous task delegation, verification, cancellation, recording/scripting, and UI testing. There are no obvious dead ends for the stated GUI automation purpose.