brand-mcp
Related Servers
Alternatives to brand-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables a constrained subagent to perform foreground GUI actions on Hyprland—observing, focusing windows, clicking, typing, scrolling, dragging, and managing the clipboard—under per-action approval with lease, audit log, and kill-switch gating.MIT
- AlicenseNot 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.1MIT
- AlicenseNot gradedqualityBmaintenanceGives each agent its own isolated nested Hyprland desktop with a private seat, clipboard and accessibility bus, so it can see the screen and drive a mouse, keyboard, touchpad gestures, windows and apps without touching the user's pointer, focus or windows. Exposes screenshots, zoom, OCR, accessibility-tree control, window management and batched actions as MCP tools, and can optionally act read-only, or with input, on the real desktop.2MIT
- AlicenseAqualityCmaintenanceEnables background window capture and input automation without moving the cursor or stealing focus, working across Windows, Linux X11, and Wayland systems.6Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to inspect and operate desktop application UI elements through platform accessibility APIs and simulated input, without relying on screenshots, across KDE Plasma Wayland, Hyprland, and Windows under a per-app allowlist.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to control Hyprland desktops via MCP, including pointer/keyboard input, screenshots, launching apps, and natural-language window targeting using a local decision model.141MIT
TDQS
Scored across 45 tools
Roughly a third of the surface is explicit duplicate aliases (open_app=launch_app, read_app_state=get_app_state, get_screenshot=screenshot, list_windows=list_apps, key=press_key, left/right/middle/double/triple_click=click, hover/move_mouse, type=type_text, left_click_drag=drag), so an agent frequently has two or more tools that do the identical thing. Overlaps also exist among non-alias tools: type_text vs type_into vs paste_text vs set_value, and screenshot vs get_app_state. The 'Compatibility alias for X' phrasing helps, but boundaries remain murky.
All names are snake_case with no camelCase mixing, which is good, but verb conventions are inconsistent: verb_noun (get_app_state, list_apps, click_text, manage_window) coexists with bare verbs (click, scroll, drag, hover, panic, wait, sequence) and bare nouns (computer, ocr, screenshot). The name 'computer' for a compatibility tool is especially uninformative and breaks any pattern.
45 tools is far beyond a comfortable set and is inflated by ~14 pure aliases that add no capability. Even discounting aliases, the 30 real tools cover a lot of ground, but the alias bloat makes the surface heavy and hard to scan.
For a Hyprland desktop-control agent the lifecycle is well covered: discovery (list_apps, list_windows), state capture (get_app_state, screenshot, ocr, get_marks), input (click, type_text, paste_text, press_key, scroll, drag, set_value), window/workspace management, and safety (security_status, request_confirmation, panic, audit_replay, sequence). Minor gaps only, e.g. no explicit clipboard read/copy-back or multi-monitor enumeration beyond cursor coordinates.