layout-debug
Related Servers
Alternatives to layout-debug
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect live web and responsive UIs across mobile and desktop sessions, returning measured text findings on contrast ratios, touch-target sizes, overflow, and theme drift instead of screenshot guesses. It also lets a human and the agent share one live panel, so the agent can navigate, tap, and type while reading the user's pinned notes and frames.98 npmMIT
- AlicenseAqualityDmaintenanceLets AI agents visually inspect web elements, test CSS edits in real-time, and iterate until pixel-perfect, functioning like browser DevTools for debugging UI issues.13 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to measure live web and responsive UIs — contrast ratios, touch-target sizes, overflow, and theme drift — and return precise findings as text with element selectors, rather than relying on screenshot guesses. Also lets an agent navigate, tap, type, and scroll in shared mobile and desktop sessions that a human watches in the same live panel and can annotate with pinned notes.98 npmMIT
- FlicenseNot gradedqualityCmaintenanceGives AI coding assistants live, structured access to running apps' state and UI elements, enabling real-time verification and interaction across web, mobile, and desktop.36-
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to visually interact with frontend apps by taking screenshots, clicking elements, reading console logs, and performing visual diffs.3 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read and manipulate visual UI designs drawn on a canvas, translating them into precise JSON specs for production code generation.11,972 npm4ISC
TDQS
Scored across 6 tools
Each tool has a distinct role, but wait_for_message and pending_requests both fetch user edits and could be momentarily confused, though the description clarifies they are listen-mode vs. poll-mode alternatives. layout_snapshot vs. selected_element are also related but distinguished by scope (full tree vs. current selection).
All names use snake_case, which is consistent, but the pattern mixes action verbs (open_window, wait_for_message, reply_in_window) with plain noun phrases for data getters (layout_snapshot, selected_element, pending_requests). Readable but two conventions coexist.
Six tools is well-scoped for a layout-debug workflow, with each tool earning a place: open, listen, inspect tree, inspect selection, drain pending edits, reply back.
The core lifecycle (open window, receive user edits, inspect the live UI, reply) is fully covered with no dead ends. A small gap is the absence of a close_window/shutdown tool and an explicit way to refresh the snapshot, but these are minor workarounds.