Human Input MCP
Related Servers
Alternatives to Human Input MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides desktop automation tools for Windows, enabling mouse and keyboard control, screenshots, clipboard management, and application interaction via the MCP protocol.43 npmMIT
- 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 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 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 gradedqualityDmaintenanceEnables AI clients to automate Windows desktop applications through window manipulation, image recognition, OCR, keyboard/mouse simulation, and memory operations via the MCP protocol.MIT
TDQS
Scored across 30 tools
The tools are grouped into human input, reading, and timer domains, and descriptions clarify many boundaries. However, several similar safety/status/cancel tools exist (human_stop, human_pause, human_mode, human_status, reading_cancel, timer_invalidate/detach), and input tools like human_activate, human_mouse_click, human_key, and human_type could still be confused without careful reading.
Names use consistent snake_case and clear domain prefixes: human_, reading_, and timer_. Most follow prefix_action or prefix_noun patterns, with minor deviations such as human_key and human_capabilities.
Thirty tools is heavy for this server, even accounting for the safety, reading, and timer subdomains. The surface feels over-granular, with many specialized status, cancellation, and timer tools that could be consolidated.
The surface covers the core human-input lifecycle: observation, targeting, pointer and keyboard actions, pause/resume/stop, event history, reading traversal, and timer coordination. Some gaps remain, such as no explicit right-click/double-click or window-focus tool, but those may be intentionally out of scope.