Skip to main content
Glama
PedroRF-tension

ask-user-rich

Related Servers

Alternatives to ask-user-rich

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to run multi-round grilling sessions in a browser UI, publishing rounds of questions with options and recommendations that users answer with buttons or free text. Supports per-question asides (re-pitch, visual diagram, plain-language explainer), chat notes between rounds, and a polling contract so sessions can stay open without blocking the client.
      17 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Provides adaptive question cards and guided multi-round interviews inside Codex, letting users clarify requirements one decision at a time and automatically sending chosen answers into the conversation.
      5
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Bridges Claude Code and OpenAI Codex CLI for an interactive plan-execute-review workflow, enabling Claude to interview, design, and review while Codex implements code changes.
      7
      29 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to research design references per page section across galleries like Awwwards, Dribbble and Mobbin, render the user's page in multiple style directions with live 3D components, and collect votes on a local board. It then produces a PDF report and iteratively builds and refines the actual page, dashboard prototype or mobile screens from that feedback.
      703 npm
      1
      MIT

    TDQS

    A4.4/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools cover distinct lifecycle stages: starting an interview, resuming a pending one, and appending to an open form. ask_user_rich and await_user_answers return identical payloads and could be momentarily confused, but the descriptions explicitly state when each applies (link delivery, failed browser open, backgrounded call).

    Naming Consistency5/5

    All three names follow a clean verb_noun snake_case pattern: ask_user_rich, await_user_answers, append_questions. Verbs are distinct and the resource (user questions/answers) is consistently implied.

    Tool Count4/5

    Three tools is minimal but each maps to a real lifecycle step (open, wait, extend), matching the narrow, single-purpose scope of a rich user-interview server. It sits at the low end of the healthy range rather than being over-built.

    Completeness4/5

    The interview lifecycle is well covered: create, resume waiting, and append follow-ups, with clear handling of deferred/needs-info states. Minor gaps exist around managing abandoned interviews (no cancel/close or list-pending operation), but the core workflow has no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues