style-agent
Related Servers
Alternatives to style-agent
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables CSS layout verification and debugging by extracting deterministic, diffable rendered layout from a browser, allowing agents to inspect, explain, and diff CSS changes.12 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables runtime CSS inspection of live web pages, providing computed styles, ASCII layout diagrams, overflow and scroll findings, plus browser interactions like screenshots, JavaScript evaluation, and CSS injection to debug actual rendering.93 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI to interact with Chrome DevTools Protocol to inspect and debug live web pages, including DOM, styles, console logs, and network requests.111,731,154 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.5,484 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.1,731,154 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceControls Chrome browser with debugging capabilities, allowing page automation, extension management, and userscript injection through the Model Context Protocol.45-
TDQS
Scored across 12 tools
Tools are mostly distinct with clear roles: find vs wait, click vs hover, styles vs inspect. However, style_status and style_tabs both list tabs, and style_styles vs style_inspect overlap in reading computed styles, creating minor confusion.
All tools share the 'style_' prefix and are lowercase snake_case, forming a recognizable pattern. Some use verbs (find, click, wait) while others use nouns (tabs, dialogs, styles), deviating from a strict verb_noun convention but remaining predictable.
With 12 tools, the set is well-scoped for a style/UI inspection purpose. Each tool covers a needed action without redundancy, fitting comfortably within the ideal 3-15 range.
The toolset covers the core lifecycle: health check, locating elements, reading styles, spacing, interactions, waiting, dialog listing, and spec-based inspection. Minor gaps such as missing screenshot or scroll capabilities are workarounds, but the surface is robust for style verification.