clawtouch-mcp
Related Servers
Alternatives to clawtouch-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceProvides MCP tools for screen capture, HID mouse/keyboard control, system and ESP status, and local Ollama chat/vision through a local MCP endpoint.-
- AlicenseAqualityBmaintenanceVerified control of the whole desktop for agents on Windows and Linux: apps with no API, windows, shell, browser. MCP server + CLI + REST API.3928MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that gives any AI assistant eyes and hands on your desktop — screenshots, clicking, typing, OCR, window management, accessibility-tree queries, workflow recording.5Apache 2.0
- AlicenseAqualityBmaintenanceWindows computer-use MCP server: accessibility-first element actions (UIA), UI read as diffed text trees instead of screenshots, guarded raw input, and a cross-session arbiter that yields to the human. 19 tools.19104 PyPI9MIT
- AlicenseAqualityCmaintenanceGives any MCP client (Claude Desktop, Cursor, and others) a Minecraft character it can actually play, exposing 34 mc_* tools for joining servers, pathfinding, mining, crafting, smelting, chest access, combat, building, chat, first-person screen viewing, and session memory. Runs over stdio or Streamable HTTP with one character per server process.34MIT
- AlicenseAqualityCmaintenanceEnables controlling a Dirtywave M8 over USB by reading its screen as text, pressing buttons, playing notes, and retrieving system information through MCP tools.7MIT
TDQS
Scored across 17 tools
Each tool targets a distinct HID gesture (move, click, hover, drag, scroll, button down/up, type, key variants, batch) and the descriptions explicitly cross-reference when to prefer one over the other (e.g. key_press vs hold_key vs drag vs manual button_down/up). The main residual overlaps are hid.release_all duplicating hid.key_release with no arguments, hid.hover being move-plus-idle, and device.status vs device.info (firmware/board vs bridge/sequence info) which are only faintly distinguished.
Names use a stable 'namespace.snake_case' scheme (hid.*, device.*) with mostly verb-based names like click, move, type, drag, release_all. Minor deviations: bare nouns/verbs like hid.key, hid.type, hid.batch, and the key vs key_press vs hold_key trio use slightly different verb styles, though the grouping remains readable and predictable.
17 tools is slightly heavy for a HID bridge but nearly every entry maps to a real primitive an agent needs (pointer, keyboard, batch, panic release, device discovery). A few could be folded (release_all vs key_release, hover vs move+duration, status vs info), keeping it just above the ideal range rather than bloated.
The surface covers the full physical-input lifecycle: pointer movement, clicking, dragging, scrolling, button hold/release, typing, key taps/holds, batched sequences, and a panic stop, plus device discovery and status. Notable gaps: hid.type refuses non-ASCII and directs callers to 'paste via the clipboard', but no clipboard tool exists, and there is no way to query the current cursor position without issuing a move.