Mozaika

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as design.mozaika/mozaika and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 27 Oct 2026. Not supplied by the maker.

• search_screens

  Search real product UI screens for design reference. Use this BEFORE designing any page/component so your output matches how the best-designed products actually solve the problem. Returns str

• get_screen_sections

  List the distinct sections of a page (hero, pricing cards, testimonial/feedback, footer, ...) so you can emulate a specific part. Each section links back to its page (parent_slug) and the prod

• list_user_flows

  List real product user flows (ordered screen journeys) — e.g. signup→dashboard, browse→checkout. Use to understand how a whole journey is structured before building it. Returns flow summaries;

• get_user_flow

  Get one user flow with its ordered steps, each including full screen metadata and image_url. Returns an error dict if the flow is not found.

• get_screen

  Get full metadata + image_url for a single screen by slug.

• get_design_system

  Get a product's full, LLM-verified design system so you can match its exact look. Use this for "design like <product>" (e.g. site="Linear", "Stripe", "Figma"). Returns (default): color_scheme

• get_design_history

  Measured design CHANGE HISTORY for a live-decoded domain — the Decode Ledger. Token-level diffs between deep decodes over time: "radius 4px→8px", "primary hover #4032C8→#0A2540", "motion domin

• audit_code

  When the user says a screen looks generic, cheap or off and you need to know WHY — paste the code and get numbers back. This is the one tool here that reads YOUR work instead of someone else's