Skip to main content
Glama
jtrslar

style-agent

by jtrslar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to style-agent

No user-submitted related servers found.

    Related Servers

    • bettercss

      ikraamg
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables CSS layout verification and debugging by extracting deterministic, diffable rendered layout from a browser, allowing agents to inspect, explain, and diff CSS changes.
      46 npm
      2
      MIT

    • browser-devtools-mcp

      kikcmime
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading browser DevTools data (tabs, console errors, network requests, screenshots, DOM, CSS, JS execution) via Chrome DevTools Protocol.
      3,661 npm
      MIT

    • Chrome DevTools MCP

      Anirbandz
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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,516,489 npm
      Apache 2.0

    • superpowers-chrome

      obra
      A
      license
      A
      quality
      A
      maintenance
      Enables direct browser control via Chrome DevTools Protocol, supporting navigation, interaction, content extraction, and screenshots through a single MCP tool.
      1
      352
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources