Connect Mozaika and your agent gets 23 tools, among them audit_code, compare_components, compare_recipes. It answers at https://mozaika.design/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Measured design systems decoded from 588 real products, for coding agents.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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 product. Give it the component's CSS, or the JS Inputs: code |
compare_components | See how the BEST products each build the same UI atom — one call, cross-product, each with its anatomy read from the live DOM. Use before building any component: compare_components("Button") returns a ranked panel (one per product) of real Inputs: component_type, industry, scheme, limit |
compare_recipes | See how the BEST products each build the same hard pattern — one call, cross-product. Use before building any complex pattern: compare_recipes("Command Palette") returns a ranked panel (one per product), each entry carrying the at-a-glance Inputs: recipe_type, industry, scheme, limit |
compare_sections | See how the BEST products each solve the same section — one call, cross-product. Use before designing any section: e.g. compare_sections("Pricing / Plans") returns a ranked panel (one per product) of real pricing sections, each with its ref Inputs: section_type, industry, scheme, limit |
generate_asset | Generate ON-BRAND icons with AI: subjects (1-12 short nouns, e.g. ["settings gear", "credit card"]) rendered in ONE consistent style. style_from is either a decoded domain ("stripe.com" — the icons match that brand's MEASURED style: accents Inputs: subjects, style_from, format |
get_asset_pack | Get a ready-made AI-generated icon pack (12 consistent icons) — e.g. a house style like 'clay-starter' / 'line-minimal-starter', or a pack generated in the MEASURED style of a decoded brand. Free and unmetered. Each image is a 1024px transp Inputs: slug |
get_component | Get one product's UI component fully specified — its anatomy read from the LIVE DOM (exact padding / height / border_radius / border / box_shadow / font_weight / letter_spacing / transition + the real :hover state) plus a reference image_ur Inputs: site, component_type |
get_design_drift | Has this product's design system CHANGED since it was decoded — and which of its numbers are safe to hard-code? Mozaika re-measures the most-referenced products from the live DOM every night and keeps a dated ledger, so this answers what a Inputs: domain |
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 dominant 150ms→200ms", each dated. Use it to see how Inputs: site |
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; colors with named roles (background, text, prim Inputs: site, format |
get_product | Pull an entire product as an agent-ready build kit: the full multi-format design system (tokens + DESIGN.md/Tailwind/CSS/JSON), every curated page, every section grouped by type (with spec + image_url), plus any user flows. Deep-decoded pro Inputs: site |
get_recipe | The universal BUILD-KIT fetcher — the measured spec + code to reproduce a piece of UI. `recipe_type` selects which library across three families (all agent-ready through this one call): • COMPONENTS (decoded live from a real product's DOM — Inputs: site, recipe_type |
get_score | Design Score: a 0-100 design audit MEASURED from the site's live DOM (real WCAG contrast pairs, detected type ladder, spacing grid, forced hover states, motion) — scored against the whole measured-web corpus ("top N% of M systems"). Free to Inputs: site, refresh |
get_screen | Get full metadata + image_url for a single screen by slug. Inputs: slug |
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 product's design system (call get_design_system(site Inputs: slug |
get_section | Get one product's specific section fully specified — its decoded spec + reference image_url + the parent product's design tokens — in a single call. Use this for "build a <section> like <product>", e.g. get_section("Linear", "Pricing / Plan Inputs: site, section_type |
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. Inputs: slug |
get_web_benchmark | The Measured Web — how the web is ACTUALLY designed, measured live across hundreds of real products (not opinions): the median design score, border-radius, body/hero font size, colour + light/dark split, spacing grid, and motion duration. U |
list_design_changes | What actually changed in the web's design systems lately — the nightly Drift Ledger feed. Mozaika re-measures ~100 of the most-referenced products every night and records a dated row per product even when nothing moved, so this is a real ti Inputs: limit |
list_my_design_systems | List YOUR private design systems (BYODS) — the sites you decoded into your own/your team's scope. Each item has name + slug; pass the slug/name to get_design_system or get_product to build against it. Returns an empty list if you have none |
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; call get_user_flow(slug) for the full ordered s Inputs: industry, query |
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 structured metadata (description, UX patterns, UI el Inputs: query, page_type, ux_pattern, industry, platform, limit |
validate_design | Grade YOUR design values against the measured corpus (hundreds of real products, decoded live — not opinions). Pass whichever metrics you have; each returns its percentile, the corpus median/p25/p75 and a verdict. Use this to anti-slop-chec Inputs: body_size_px, hero_size_px, base_unit_px, radius_px, dominant_duration_ms, container_max_width_px |
Every block below points at https://mozaika.design/mcp. Pick your client and copy.
claude mcp add --transport http mozaika https://mozaika.design/mcp
{
"mcpServers": {
"mozaika": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mozaika.design/mcp"]
}
}
}{
"mcpServers": {
"mozaika": {
"url": "https://mozaika.design/mcp"
}
}
}{
"servers": {
"mozaika": {
"type": "http",
"url": "https://mozaika.design/mcp"
}
}
}{
"context_servers": {
"mozaika": {
"url": "https://mozaika.design/mcp"
}
}
}{
"mcpServers": {
"mozaika": {
"serverUrl": "https://mozaika.design/mcp"
}
}
}{
"mcpServers": {
"mozaika": {
"url": "https://mozaika.design/mcp"
}
}
}name: Mozaika
version: 0.0.1
schema: v1
mcpServers:
- name: Mozaika
type: streamable-http
url: https://mozaika.design/mcp{
"mcpServers": {
"mozaika": {
"httpUrl": "https://mozaika.design/mcp"
}
}
}{
"mcpServers": {
"mozaika": {
"type": "http",
"url": "https://mozaika.design/mcp"
}
}
}{
"mcpServers": {
"mozaika": {
"url": "https://mozaika.design/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmozaika.design%2Fmcp&type=streamable_http&id=mozaika&name=Mozaika
It answered our last check on 18 October 2026 in 52 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by mozaika.design and served from mozaika.design, the vendor's own domain: https://mozaika.design/mcp.
23, as returned by the server's own tools/list on 31 August 2026: audit_code, compare_components, compare_recipes, compare_sections, generate_asset, get_asset_pack, get_component, get_design_drift, and 15 more.
It answered our last check on 18 October 2026 in 52 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mozaika.design/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: design.mozaika. Endpoint host: mozaika.design. ARD identifier: urn:air:design.mozaika:mcp:mozaika.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.