Design review as MCP tools: critique, states, journeys, UI copy, PRD assumptions. BYOK or hosted.
Scored across 6 tools
Each tool targets a fairly distinct UX-review activity (copy, terminology, design critique, assumptions, state matrix, journeys). The only real overlap is between audit_copy and critique_experience, since copy is also one axis of the broader design critique, but the per-string vs whole-design framing mostly separates them.
All six tools follow a clean verb_noun snake_case pattern (audit_copy, check_terminology, critique_experience, find_assumptions, generate_state_matrix, map_journey). No mixed conventions or vague single-word names.
Six tools is well-scoped for a design/UX critique server, with each tool clearly earning its place and no redundant filler. The count is neither thin nor bloated.
The surface covers a strong range of critique angles: copy, terminology drift, design health, assumptions, state coverage, and journeys. Minor gaps exist (e.g. no accessibility-specific lens or tool to persist/compare findings across reviews), but an agent could work around these.
Per-string critique of interface copy: buttons, errors, empty states, confirmations, notifications. Each string comes back with the problem and a fix, or nothing if it already works. Call it before shipping UI strings.
Inputs: strings (required).
Finds concepts that carry different names across surfaces (UI strings, docs, API reference, support macros) and flags drift. Pass the text from each surface; nothing needs connecting.
Inputs: sources (required).
Adversarial critique of a design, given as a description or a screenshot URL, with an optional PRD. Returns findings ranked by severity covering hierarchy, density, affordance, composition, copy, and the first-use / 500th-use / zero-data / huge-data / no-permission / irreversible questions. Call it before presenting a design to a human or handing it to engineering.
Inputs: artifact (required), prd, context.
Reads a PRD or design brief and extracts the unverified assumptions inside it, ranked by risk, each turned into a research question that could change a decision. Never simulates user answers.
Inputs: prd_text (required).
Generates the state space for a feature, form or screen across data, loading, permission, network, account, content, time, concurrency, outside dependencies, money, consistency and people, and lists the gaps most likely to cause real harm. Call it when a feature is described and you want to know what nobody drew.
Inputs: feature_description (required), known_dimensions.
Breaks a user objective into the stages of a real journey and flags entry points and exit paths that have no designed arrival or recovery. Optionally focuses on one user maturity (first use, occasional, habitual, expert). Describes behavior, not screens.
Inputs: objective (required), user_maturity.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Governed MCP workflow automation for MSPs and agencies: approvals, durable state, signed evidence.
Human-in-the-loop review and approval for AI agents. Audit trail, approval policies, native MCP.
Paid remote MCP for AI Studio Workspace approval gate MCP, structured receipts, audit logs, and revi
Design review for UI code and live pages: quick checks, 0-100 scored reviews, fixes as patches
Add one secure layer between your agents and this server.
