Skip to main content
Glama

Related Servers

Alternatives to phyll

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP-first UI/UX review layer for AI-generated frontends. Enables reviewing web pages via URL, capturing screenshots, extracting layout metrics, and generating structured repair plans for agents.
      22 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to act like a senior UI/UX team by reading an existing site's design DNA and tokens, proposing distinct art directions and motion mechanics that fit the brief, and validating changes in a live headless Chromium browser. Provides per-element accessibility and performance auditing (WCAG 2.2 contrast, focus, clipping, phone-menu behavior, LCP/CLS) at multiple viewport widths, plus baseline capture, before/after comparison, and one-command rollback for safe redesigns.
      77 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      268 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Lets an AI agent drive live mobile and desktop sessions of a web page and receive measured UI findings — contrast ratios, touch-target sizes, overflow and theme drift — as actionable text tied to specific selectors, rather than guessing from screenshots. A shared panel keeps the human and agent on the same live view, where pinned notes and frames can be read back by the agent.
      268 npm
      MIT

    TDQS

    A4/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools map cleanly to distinct phases of the review workflow, such as starting, interacting, capturing evidence, and finishing. The only mild overlap is among capture, screenshot, and probe, but their descriptions clarify when each should be used.

    Naming Consistency4/5

    The majority of tools use short lowercase imperative verbs like click, fill, open, and resize, which is readable and predictable. There are minor deviations such as account as a noun and the underscored compounds start_review and finish_review, but the overall style remains consistent.

    Tool Count4/5

    Eighteen tools is slightly above the ideal range, but the count is justified by the breadth of browser interactions and review steps the server supports. Each tool covers a distinct capability and none feel redundant.

    Completeness4/5

    The tool set covers the full review lifecycle: start, navigate, interact, capture evidence, measure, and finish, plus account and upgrade support. Minor gaps like no explicit cancel-review or previous-report listing exist, but they do not block the core workflow.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing