UserFlow MCP
Related Servers
Alternatives to UserFlow MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceDeploys AI user personas to validate user journeys at scale, surfacing UX friction before real users encounter it.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to scan deployed web apps by sending a flock of AI users that identify UX issues, mobile breakage, and conversion path problems, returning prioritized, fix-ready findings.MIT
- AlicenseNot gradedqualityDmaintenanceYour AI coding agent tests pages, copy, and flows on simulated users while building.1MIT
- AlicenseAqualityAmaintenanceAI-powered exploratory QA agent. Explores web apps like a real user — 18 MCP tools for clicking, filling forms, and navigating. Automatically verifies that actions persist (fake deletes, failed edits). Runs 16 detection types including dead links, SEO, accessibility, and performance checks.292MIT
- AlicenseNot gradedqualityAmaintenance▎ Enables AI assistants to unleash a crowd of role-played virtual users — impatient shoppers, seniors, keyboard-only users, privacy hawks, chaos monkeys — on a website. Each persona browses in a real Chromium browser, files UX/QA findings in character, and the site receives a damage report with an S–F survival grade. Accusations can be cross-examined by up to three independent verification engines2MIT

autousersofficial
AlicenseAqualityBmaintenanceEvaluate UX with AI personas and human raters directly from MCP-aware clients like Claude and ChatGPT.390MIT
TDQS
Scored across 14 tools
Most tools have distinct purposes: session control (start/step/end), observation (get_page_state), analysis (accessibility_audit, inspect_storage, export_har, compare_screenshots), and persona/device management. The only possible confusion is between start_session and quick_scan, both navigate but one establishes a session; descriptions clarify this. Overall, tools are well-differentiated.
Tool names are predominantly verb_noun (start_session, get_page_state, create_persona), but some deviate with adjective_noun or single-word names (quick_scan, auto_walk, step). All use snake_case, which maintains readability, but the inconsistency in grammatical pattern reduces predictability.
14 tools cover the full user flow testing lifecycle without feeling bloated. Each tool addresses a specific concern: session control, page inspection, accessibility, storage/network analysis, persona management, and automated comparisons. The count is appropriate for the comprehensive feature set.
The tool surface covers the core lifecycle (start/step/end), plus useful extensions like accessibility audits, storage/HAR inspection, and persona-based automated testing. Minor gaps exist (no update/delete persona, no resize viewport beyond device profiles), but they don't hinder the primary use case. Overall, the domain is well-covered.