elementor-live
Related Servers
Alternatives to elementor-live
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to see and interact with real Chrome pages through structured DOM inspection, targeted screenshots, recordings, and human-in-the-loop approvals across major coding-agent hosts.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to read the user's real logged-in Chrome session, returning stability-ranked and uniqueness-verified selectors, annotated screenshots, page objects, design tokens, accessibility checks, and QA diagnostics. Actions that change the page are proposed to the user for in-page approval before anything happens.221,144 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to control the user's real Chrome or Firefox tabs, with their existing logins, to read pages, click, type, fill forms, take screenshots, inspect network traffic and run JavaScript. It works through a paired browser extension over a local WebSocket connection, so automation happens in the browser the user is actually looking at, including shadow DOM, cross-origin iframes, dialogs and single-page apps.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding agents to visually interact with frontend apps by taking screenshots, clicking elements, reading console logs, and performing visual diffs.6 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read, build, refactor, and govern Elementor websites through a Model Context Protocol server and companion WordPress plugin with atomic validation, backups, and rollback.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to capture pixel-accurate screenshots and DOM state from localhost apps, receive user-drawn instructions and reference images, and manage implementation review cycles.7 npmMIT
TDQS
Scored across 14 tools
Most tools target clearly distinct resources or actions (skeleton vs. single-element inspect, mutate vs. save, widgets vs. controls). There is mild overlap in the user-event area: get_canvas_skeleton also returns recent events, get_user_activity is a dedicated event feed, and wait_for_user_prompt surfaces Alt+Space prompts, so an agent could pick the wrong one. canvas_status and open_editor also both return the same status object, though the descriptions sequence them clearly.
The dominant pattern is snake_case verb_noun (get_canvas_skeleton, list_widgets, inspect_element, save_document, capture_vision, open_editor, mutate_canvas). A few deviate to noun_verb or noun_state forms (canvas_status, design_lint, agent_say, set_hud), but names remain readable and largely predictable. Minor inconsistency, not confusing.
14 tools is well within the healthy range and each has a distinct role: session setup, discovery, mutation, verification, and user interaction. Nothing feels padded; even the UX tools (set_hud, agent_say) serve the live-editor collaboration model.
The surface covers the full edit lifecycle: connect, discover widgets/controls, read tree and element detail, batch create/update/move/delete/duplicate/custom CSS, save, screenshot-verify, and lint. Gaps exist: no media library/upload tool (images must already exist as attachment IDs), no document/page-level settings or global styles access, no history/undo tool (relies on the user pressing Ctrl+Z), and no template save/insert.