Uxloom MCP server

Read from the package source without running it. The installed server may list more.

• brief_answerwrite action

  Submit brief answers. Unanswered fields take researched defaults and are recorded in the assumption ledger (auditable, reversible).

• brief_start

  Start a design brief. Returns a structured questionnaire. Answer every question you can yourself — from the provided context document (PRD, spec) first, then conversation context; only relay questions marked askHuman:true to the user. Then call brief_answer.

• comment_context

  The full work packet for one reviewer comment: the comment, the exact layout block its pin lands on, the complete screen definition (contract, components, layout, rationale, exemptions), every journey state referencing that screen with its transitions, and the current validation findings scoped to that screen. Use it to address the comment precisely, then call comment_resolve.

• comment_resolve

  Resolve a reviewer comment after addressing it. The resolution note is shown to the reviewer and persisted; the pin clears live in every open preview. Never resolve without actually making the change.

• comments_list

  Reviewer comments from the preview, with lifecycle status. Comments the reviewer clicked "→ agent" on are ASSIGNED — they are your work queue: call comment_context for each (assigned first, then open), make the change, then comment_resolve. Check this at session start and after every validation run.

• coverage_report

  The demo number: screens delivered vs. states the journeys actually need. Returns per-screen coverage and the missing-state list.

• design_audit

  Reverse bridge (RFC 0007): audit a design export against the contract. Point it at a Figma/Penpot SVG or JSON export, a folder of them, or a uxloom `--manifest` index.json. Recovers screen×state from frame names (grammar "<Screen> / <state>", or the manifest) and reports which required screens/states have no frame: design-screen-unmapped, design-state-missing, design-frame-unmapped. Optional scaff

• design_review

  One iterative design-review round (max 3 per project — enforced). Computes validation + rationale coverage, persists the round with deltas to <project>.reviews.json, and returns a structured rubric to critique the design against: completeness, evidence, consistency, market fit, accessibility, honesty. Address the rubric, improve the design, then call again. Round 4 is refused: present results to t

• journey_define

  Add or replace a journey (a state machine: states reference screens, events move between states). Screens referenced here must be registered via screen_register before project_validate passes.

• palette_check

  Check a design system's color pairs against WCAG 2.2 AA (4.5:1) before any screens exist. Reports each pair's exact ratio, pass/fail, and thin-margin passes (under 5.0:1) that one shade lighter would break.

• project_audit

  Audit the implementation against the design contract (drift detection). Static tiers: the uxloom.map.json screen registry and data-ux-screen/data-ux-state markers in source. Returns per-state verdicts (implemented with file:line evidence / unimplemented / unproven) and findings with fixes. When implementing screens from the contract, emit data-ux-state markers so the code stays self-auditing.

• project_export

  Return the complete current project document (for inspection, backup, or transformation before a project_import).

• project_import

  Replace the whole project in one call: journeys and screens together. Prefer this over many journey_define/screen_register calls when registering a complete or large design. Validates the full document; unknown fields are rejected.

• project_initwrite action

  Create a new UXLoom project file (uxloom.project.json). Run once per product.

• project_validatewrite action

  Run every critic: journey completeness (unreachable states, dead ends, broken transitions), state coverage, WCAG contrast, touch targets, text expansion — plus fragment-merge errors and open reviewer comments from the preview. Honors uxloom.config.json thresholds. Iterate until errors = 0 and reviewer comments are addressed.

• screen_critique

  Findings scoped to a single screen. Use during iteration on one screen.

• screen_register

  Add or replace a screen: its intent, requiredStates (the contract), designedStates (progress), and components with colors/labels/target sizes for the critics.

• Code scan49 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 45 days ago12/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

78/100

higher than 57% of 4,460 AI and agents servers

Tools

17

the typical AI and agents server has 6

Tools that change things

18%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

1

more than 50% of 2,711 AI and agents servers

Downloads a week

56

more than 46% of 1,538 AI and agents servers with a package

Uxloom: common questions

Is Uxloom MCP server safe?

Mostly: it is graded B (78/100). Read the Uxloom safety report

How do I install Uxloom?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Uxloom need an API key?

No secret keys are declared. It reads 1 setting from the environment.

Is Uxloom maintained?

The last commit was 87 days ago (2026-08-09). The latest release is v0.14.0.

What can I use instead of Uxloom?

Servers from other publishers that do the same job: Agent-Native Design MCP server, Kiln MCP server and Figma Context MCP server.

How does Uxloom compare with other AI and agents MCP servers?

safety score 78/100 (higher than 57% of 4,460 AI and agents servers); tools 17 (the typical AI and agents server has 6); tools that change things 18% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.