Refero organizes screenshots for humans. Mozaika decodes design systems for agents.
Both plug into your AI agent over MCP. Refero's MCP hands your agent references to look at. Mozaika's MCP hands it measured specs to build with — hex tokens, type scales, spacing rhythm, decoded per section from 588 real products.
This is a static, crawlable rendering for search & AI engines. The interactive version — filters, live decode console, copy & export — is at https://mozaika.design/vs/refero.
Feature by feature
Built for
Mozaika: AI coding agents (Claude Code, Cursor) that need machine-readable specs
Refero: Designers doing visual research; agent support added on top
What an MCP query returns
Mozaika: A decoded design system: color tokens, type scale, spacing — per section
Refero: Curated screens, flows and patterns — reference images for the agent to study
Section-level decode
Mozaika: Yes — 3,873 retina sections, each queryable with its own decoded specs
Refero: No — screens and pages as curated images
Measured design systems
Mozaika: 548 decoded, 412 measured and verified against live CSS
Refero: Fonts info and Styles (beta); no per-section measured token specs listed
Library size
Mozaika: 3,873 sections, 548 design systems, 588 products — curated depth over volume
Refero: 135,000+ screens across web and iOS — significantly larger
User flows
Mozaika: No — page- and section-level today
Refero: Yes — step-by-step flows
Decode any live site
Mozaika: Yes — Decode Lens Chrome extension reads tokens off any URL
Refero: No equivalent listed
Pricing
Mozaika: Free gallery browsing; Pro subscription or one-time Founder license for lifetime access
Refero: Free (~3% of library); Pro $10/mo or $120/yr; no lifetime plan listed
When to choose Refero — honestly
If you're a designer doing visual research, Refero is excellent and we'll say so plainly: 135,000+ screens across web and iOS, real signup-to-cancellation flows, fonts info, and a polished search experience — at $10/month it's a fair deal. If your main workflow is a human browsing references before designing in Figma, choose Refero. Mozaika is the better tool when the consumer of the reference is an AI coding agent that needs numbers, not pictures: exact tokens, type scales, and spacing it can build against without inventing its own.
Questions people actually ask
Is Mozaika a Refero replacement?
Only if your use case is agent-driven building. Refero is a research library for humans with agent access added; Mozaika is built agent-first — every product is decoded into a queryable design system at the section level. Some teams use both: Refero to browse, Mozaika to build.
Both have an MCP. What's actually different?
What comes back over the wire. Refero's MCP connects your agent to curated screens and flows — visual references. Mozaika's MCP returns decoded specs: hex color tokens, measured type scales, spacing systems, per section. Your agent doesn't interpret a screenshot; it builds to a spec.
Isn't Mozaika's library much smaller?
Yes — 588 products versus 135,000+ screens, and we won't pretend otherwise. The trade is depth per product: 1,768 full pages sliced into 3,873 retina sections, with 548 decoded design systems, 412 of them measured and verified against live CSS. Curated and decoded beats big and flat when an agent is doing the reading.
Does Mozaika offer a lifetime option?
Yes — alongside a Pro subscription, there's a one-time Founder license for lifetime access. Refero's pricing page lists no lifetime option (as of July 3, 2026).