eyes-mcp
Related Servers
Alternatives to eyes-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to capture screenshots, inspect windows, and interact with the Hyprland desktop environment through mouse clicks and keyboard input.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to capture screen regions by defining a visual overlay or arbitrary coordinates, returning base64 PNG images.31 npmMIT
- FlicenseAqualityCmaintenanceGives AI agents eyes on Hyprland Wayland desktops by capturing screenshots via grim and offering optional image analysis with Gemini API.6-
- AlicenseNot gradedqualityDmaintenanceEnables screenshot capture and visual analysis using cloud or local vision models, with tools to describe screens, list windows, and analyze images.151 npm14MIT
- AlicenseNot gradedqualityDmaintenanceLets an LLM see what's on your screen by capturing an entire monitor or a specific application window.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to control a Hyprland Wayland desktop by listing windows, capturing screenshots, and sending input to a dedicated agent workspace without disrupting the user's screen.-
TDQS
Scored across 8 tools
The four capture tools target distinct scopes (monitor, active window, matched window, arbitrary region), and the list tools cover distinct resources (windows, monitors, captures). capture_active_window vs capture_window could be briefly confused since both capture a window, but descriptions clarify the difference (focused vs class/title match).
All names follow a clean verb_noun snake_case pattern: capture_* for screenshots, list_* for enumeration, cleanup_* for deletion. The convention is applied uniformly with no deviations.
Eight tools is well-scoped for a screen-capture utility, with each tool earning its place across capture targets, discovery, and session cleanup. No redundant or filler tools.
The surface covers capture across monitor/window/region plus discovery (list_windows, list_monitors) and lifecycle management (list_captures, cleanup_captures), which is strong. Minor gaps like delayed/timed capture or annotation are absent but not essential to the core workflow.