Skip to main content
Glama
thiagown1

UI Journey MCP

by thiagown1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to UI Journey MCP

No user-submitted related servers found.

    Related Servers

    • FlowLens MCP Server

      magentic
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables coding agents to access recorded browser flows (user actions, network, console, etc.) for debugging and regression testing without reproducing issues.
      110
      Apache 2.0

    • heimdall

      AntreasAntoniou
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to author, validate, and execute browser/API test plans with parallel drivers, assertions, and captured evidence such as screenshots and network logs.
      MIT

    • why-ui

      Yudis-bit
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to inspect live browser runtime evidence, such as blocking elements and interaction surfaces, and to independently verify whether a code fix resolved the issue.
      57 npm
      1
      MIT
    • uxloom by uxloom-dev

      uxloomofficial

      uxloom-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to validate UI designs for missing states, accessibility issues, and journey completeness using state machine modeling.
      17
      1
      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 9 tools

    Disambiguation4/5

    Each tool has a fairly distinct purpose: listing, fetching metadata, fetching evidence, comparing revisions, tracing paths, and finding impact/coverage gaps. Some overlap exists between get_flow_evidence and get_change_evidence, and between get_ui_impact and get_coverage_gaps, but descriptions clarify retrieval vs. discovery and revision vs. PR context.

    Naming Consistency5/5

    All nine tools follow a consistent snake_case verb_noun pattern (list_flows, get_flow, compare_flow, trace_journey, get_evidence_image), with no mixed casing or verb styles.

    Tool Count5/5

    Nine tools is a well-scoped set for a UI journey/evidence server, covering discovery, inspection, comparison, tracing, and impact analysis without bloat.

    Completeness4/5

    The surface covers the lifecycle of mapping, retrieving, comparing, tracing, and gap analysis, but lacks explicit create/update/delete operations for flows or mappings, so agents cannot mutate mappings through this server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources