som-window-mcp
Related Servers
Alternatives to som-window-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceGives MCP-capable AI tools running on Windows sight of the user's desktop: it captures the window being looked at, any monitor, window or region, and offers OCR, text finding, full-resolution zooming, snips, hotkey marks, visual baseline comparison and waiting for screen changes. Sensitive apps and windows are blacked out before any image reaches the AI client.MIT
- AlicenseNot gradedqualityCmaintenanceGives an agent eyes and hands on Windows desktops: screenshots with grids and Set-of-Marks, offline OCR with word boxes, click_text, mouse/keyboard/drag/window control, UI Automation, and batched act-and-verify actions. Supports a read-only mode that disables all input plus per-action audit logging.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read what is on a Windows desktop as text — open windows, their contents, and what changed — using Win32 and UI Automation with optional NPU vision. Secrets, password fields, and private windows are withheld and personal data scrubbed on the user's PC before anything reaches the agent.AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read any Windows window as text with coordinates, including control names, roles, clickability, and all on-screen text positions, so even models without vision can understand and act on the desktop. It is read-only, listing windows, finding elements by name, and waiting for text to appear, without clicking, typing, or stealing focus.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to observe Windows desktops through screenshots, UI Automation trees, a live pixel grid, and token-efficient delta canvas updates without clicking or typing.1AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceLets an AI model see an indexed UI Automation accessibility tree of Windows desktop apps and act on it with precise clicks, typing, key chords, scrolling, dragging, and element value changes, using window captures that work even for occluded windows. Screenshot-based coordinates are rescaled and validated against the target window so input fails loudly instead of hitting the wrong app.MIT
TDQS
Scored across 5 tools
The five tools target distinct stages of window inspection, but there is some inherent overlap: get_ui_tree and inspect_element both read the UIA tree at different granularities, and capture_window and capture_som both return screenshots. The descriptions explicitly clarify when to use the marked capture or element-level inspection, so an agent can usually choose correctly.
All tool names use consistent snake_case with clear verb_noun forms: list_windows, get_ui_tree, inspect_element, capture_window, capture_som. The verbs are predictable and the nouns identify the resource or output type.
Five tools is well-scoped for a focused window-inspection server. Each tool covers a distinct capability: enumeration, tree reading, element detail, plain capture, and marked capture.
The surface covers the read-only inspection lifecycle well: list windows, inspect their UI trees, drill into elements, and capture plain or marked images. The main gap is the absence of any interaction or action tools such as clicking or typing, which an agent may expect from a window-automation server.