Design

mozaika.design

Provides real product UI screens for design reference and user flow analysis.

1 endpoint23 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mozaika.design/mcp

No auth detected

MCP server metadata

Name: mozaika
Version: 1.29.1

Capabilities

experimentalpromptsresourcestools

Server instructions

Mozaika answers one question — how do real, well-built products actually do this, as numbers rather than adjectives. Every value here is measured from a live DOM (colour roles, type scale, spacing grid, radii, button hover/focus states, shadows, motion durations and easings, component anatomy), or aggregated from a corpus of those measurements. REACH FOR IT when the user asks you to build or restyle anything visual — a page, a section, a component, a set of design tokens — or says a screen looks generic, cheap or unfinished. Use it before you write the CSS, not after. IF THE SCREEN IN QUESTION IS THEIRS, start inward: audit_code(code="<the component's CSS or its JSX with class attributes>") measures what that code actually contains and grades it against the corpus, worst-first. It is the only tool here that reads your work rather than another product's, it is free, and it is the shortest path from "this looks wrong" to a number you can act on. SKIP IT for backend, API, data, tests, CI, infra, and refactors with no visual output. It also cannot see your repository, your running app or your logs, so read the code first: the app's own existing design language outranks any outside reference. IF NO PRODUCT IS NAMED, work by type rather than by brand — compare_sections("Pricing / Plans") · compare_components("Button") · compare_recipes("Command Palette") each return a cross-product panel to choose a direction from. get_web_benchmark() gives the web's median values, and validate_design(body_size_px=..., radius_px=...) grades numbers you already have against the corpus. IF A PRODUCT IS NAMED: get_design_system("Linear") for the whole system, or get_section / get_component / get_recipe(site, type) for one piece of it. COST: search, the benchmark and the drift reads are free and unmetered. Measured decodes cost one call from a free account's 25 per month, and full decodes on a free account are limited to a rotating shelf of 30 products; a refused call is never billed. Three to six calls is a normal budget for one task.

Known tools 23

search_screens

Search real product UI screens for design reference.

Inferred read-only

get_screen_sections

List the distinct sections of a page (hero, pricing cards, testimonial/feedback, footer, .

Inferred read-only

list_user_flows

List real product user flows (ordered screen journeys) — e.

Inferred read-only

get_user_flow

Get one user flow with its ordered steps, each including full screen metadata and image_url.

Inferred read-only

get_screen

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

Inferred read-only

get_design_system

Get a product's full, LLM-verified design system so you can match its exact look.

Inferred read-only

get_design_history

Measured design CHANGE HISTORY for a live-decoded domain — the Decode Ledger.

Inferred read-only

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.

Inferred read-only

validate_design

Grade YOUR design values against the measured corpus (hundreds of real products, decoded live — not opinions).

Inferred read-only

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.

Inferred read-only

get_design_drift

Has this product's design system CHANGED since it was decoded — and which of its numbers are safe to hard-code?

Inferred read-only

list_design_changes

What actually changed in the web's design systems lately — the nightly Drift Ledger feed.

Inferred read-only

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.

Inferred read-only

compare_sections

See how the BEST products each solve the same section — one call, cross-product.

Inferred read-only

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_url and the product's design tokens, in a single call.

Inferred read-only

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.

Inferred read-only

get_recipe

The universal BUILD-KIT fetcher — the measured spec + code to reproduce a piece of UI.

Inferred read-only

compare_recipes

See how the BEST products each build the same hard pattern — one call, cross-product.

Inferred read-only

get_product

Pull an entire product as an agent-ready build kit: the full multi-format design system (tokens + DESIGN.

Inferred read-only

list_my_design_systems

List YOUR private design systems (BYODS) — the sites you decoded into your own/your team's scope.

Inferred read-only

get_asset_pack

Get a ready-made AI-generated icon pack (12 consistent icons) — e.

Inferred read-only

generate_asset

Generate ON-BRAND icons with AI: subjects (1-12 short nouns, e.

Inferred read-only

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").

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mozaika]
url = "https://mozaika.design/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mozaika": {
      "type": "http",
      "url": "https://mozaika.design/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mozaika
Remote MCP URL: https://mozaika.design/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mozaika": {
      "url": "https://mozaika.design/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mozaika": {
      "type": "http",
      "url": "https://mozaika.design/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mozaika",
  "transport": "streamable-http",
  "url": "https://mozaika.design/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for mozaika.design was fetched 2026-08-05T10:48:17.647Z and is being refreshed.

Trust status VerificationRecommended

mozaika.design is assessed as VerificationRecommended: Domain has affiliate links on record

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.