Scoreboard · 8 tools · 6 criteria
Which design libraries can your agent actually use?
“AI-ready” is on everyone's homepage now. This scoreboard checks what's underneath, for the tools an AI-coding builder actually shortlists: does an MCP exist, can an agent try it free, does it return something buildable, and do the terms survive an automated workflow? Every non-obvious cell carries a source. Mozaika is graded with the same knife — gaps included.
01 · The scoreboard
Six questions, asked of everyone.
| Tool | MCP exists? | Free tier on the MCP? | What the agent receives | Call caps | Monthly billing? | Agent-license clarity | Verdict |
|---|---|---|---|---|---|---|---|
| Mozaika that's us — read accordingly |
●HTTP MCP at mozaika.design/mcp; listed in the official MCP Registry | ●25 calls/mo, no card · search unmetered · 30-system rotating open shelf | Measured specs from the live DOM: type size/weight/tracking, color roles + usage, spacing, radii · DESIGN.md / Tailwind / CSS vars / W3C tokens | Free: 25/mo (gated calls never counted). Paid: flat — no credits, no meters | ●$9/mo · $60/yr · $59 once (founder lifetime) | ●Plain: what you or your agent build from specs is yours, commercial use, no attribution | BUILD-READY — but web-only, ~330 products, launched 2026 |
| Mobbin category giant |
●Launched May 11, 20261 | ◐Not stated in docs we reviewed; free account = latest 4 apps/sites2 | “Screen images inline” — reference pictures, agent estimates values from pixels3 | Not stated3 | ○Yearly (~$120 upfront) or quarterly only2 | Not stated for agent output in docs we reviewed | REFERENCE-READY, NOT BUILD-READY — unbeatable breadth (621,500+ screens, mobile)1 |
| Refero fast riser |
●Hosted MCP, 8 tools, launched Mar 20264 | ○Free plan explicitly excludes MCP, Skill & Figma plugin5 | Screens + AI-generated style pages — inferred from screenshots; styles cover marketing/landing pages only6 | Not stated4 | ●$17/mo (or $10/mo annual)5 | Not stated for agent output in docs we reviewed | AGENT-READY IF PAID — specs generated, not measured; strong library incl. ~65k iOS4 |
| Nicelydone SaaS-web specialist |
●First-party MCP, 12 tools (screens, flows, components, collections)7 | ○No free hook — MCP requires a paid account7 | Screenshot references + metadata/tags — not measured specs7 | Not stated7 | ○Solo $15/mo billed yearly (~$180); quarterly toggle8 | Not stated for agent output in docs we reviewed | REFERENCE-READY, PAID-ONLY — deep SaaS web archive (237k+ screens)8 |
| Page Flows video flows |
○None — MCP Registry query returns empty; no API; llms.txt 4049 | ○n/a | Nothing machine-readable — screen-recorded videos for human viewing9 | n/a | ○Quarterly $39 or yearly $99; no free tier; $2.95 3-day trial auto-converts10 | n/a | NOT AGENT-ACCESSIBLE — valuable video research for humans |
| 21st.dev Magic component marketplace |
◐Magic MCP exists; reliability issues reported in Claude Code (open GitHub issues #69 “[object Object]”, #70 500s)11 | ◐2 MCP searches/day on the free plan12 | Component code snippets — searchQuery capped at 2–4 words, snippet returned without design-system context11 | Free: 2/day; AI generation runs on paid credits12 | ◐Community ~$8/mo, billed quarterly12 | Marketplace terms; not stated per-component for agent use | PARTIALLY READY — snippets, not systems; check the open issues first11 |
| Untitled UI biggest Figma kit |
●First-party MCP + CLI shipped with React v8.013 | ◐Open-source React tier is free; PRO components need a one-time license13 | Installs their own components (one house style) — cannot describe third-party sites' design13 | Not stated13 | ○One-time licenses ($139–$999 Figma tiers, July 2026)14 | ◐One-time purchase, lifetime updates; agent-specific terms not stated14 | READY — FOR ITS OWN KIT. Different job than a reference library |
| Relume marketing-site system |
●Official Relume Library MCP (2026)15 | ○MCP on paid plans only15 | Their own component code — “Real components, not hallucinations” (their words); one library's style15 | Not stated15 | ●Design $49/mo · Build $99/mo16 | Not stated for agent output in docs we reviewed | READY — FOR ITS OWN KIT, PAID. Webflow-workflow strength |
Grading ourselves with the same knife
Mozaika's real gaps, July 2026: the library is ~330 web products / ~2,900 measured sections — a fraction of Mobbin's 621,500+ screens or Nicelydone's 237k. There is no mobile coverage at all. We launched in 2026: no eight-year archive, no big community, and you should weigh a young vendor's longevity like you would any other. What we'd argue back: the six columns above are about what an agent receives — and measured, per-section specs with a free tier is the combination nobody else on this board offers yet.
02 · Reading the board fairly
One honest paragraph per tool.
Best payload on the board for building (measured specs, 4 export formats), only real free MCP tier, cheapest paid step ($9/mo or $59 once). Smallest library, web-only, newest vendor. If you need breadth or mobile, pair us with a giant — or skip us.
The strongest research library ever assembled in this category — 8 years, weekly updates, real shipped UI. Its MCP mirrors its nature: reference images for inspiration, not values for construction. Billing is annual/quarterly only, a documented user sore point.
The most aggressive AI pivot in the category (MCP + Skill + Figma + styles) and growing fast. The style layer is AI-inferred from screenshots and scoped to marketing pages per their docs — fine for inspiration, weaker as a build contract. Fair monthly pricing.
A decade of SaaS web-app captures with a genuinely capable 12-tool MCP — the closest structural cousin to ours. Payload is references and metadata rather than measurements, and there's no free way for an agent to try it.
Video walkthroughs of real journeys — a research format nothing else here replicates. But there is no machine surface at all (no MCP, no API, llms.txt 404), and the $2.95 auto-converting trial has generated documented billing complaints.
The first mover on “components over MCP” and still the fastest way to grab a pretty React block. The contract is thin — 2–4-word queries, context-free snippets — and Claude Code reliability issues were open on GitHub as of July 2026.
The strongest AI story in the kit world: MCP + CLI that installs its own well-made components. It solves “give me good parts,” not “what makes Stripe's pricing page work.” One-time pricing is refreshingly simple.
Excellent for Webflow-centric marketing-site teams; the MCP serves its own 1,500+ components. Its most-repeated public criticism is “generic” output — a style ceiling, not a tooling failure — and agent access requires a paid plan.
03 · Sources
Where every cell comes from.
Source notes — all checked July 2026 unless dated otherwise
- Mobbin MCP launch — BusinessWire press release, May 11, 2026 (“621,500 Real App Screens to Reference”); mobbin.com/mcp (“Trusted by 2M+ designers”).
- Mobbin pricing — mobbin.com pricing page: free = latest 4 apps/sites, 3 collections; Pro billed yearly (~$120) or quarterly; no monthly. Echoed in public user threads.
- Mobbin MCP payload — Mobbin MCP documentation: “returns screen images inline.” Caps/licensing for agent use not stated in the docs we reviewed.
- Refero MCP — Product Hunt launch, March 10, 2026; hosted at api.refero.design/mcp; 8 tools incl. refero_search_styles / refero_get_style.
- Refero plans — doc.refero.design/help/plans: free plan excludes MCP, Skill and Figma plugin; Pro $17/mo or $10/mo billed annually.
- Refero styles scope — Refero documentation: styles cover marketing/landing pages; in-app dashboards, auth, settings excluded as style systems; style pages generated from screenshots.
- Nicelydone MCP — first-party MCP with 12 tools (search screens/flows/components, collections), 2026; access requires a paid account (no free agent hook found).
- Nicelydone library/pricing — nicelydone.club: 237,100+ screens, 12,300+ flows from 500+ SaaS apps; Solo $15/mo billed yearly.
- Page Flows agent surface — official MCP Registry API query for “pageflows” returns empty (verified 2026); pageflows.com/llms.txt returns 404; no public API found.
- Page Flows pricing — pageflows.com pricing page: $2.95 3-day trial auto-converts, quarterly $39, yearly $99; auto-conversion complaints in public reviews.
- Magic MCP contract & reliability — 21st.dev Magic MCP tool schemas (searchQuery “two-four words max”; returns snippet only); GitHub issues #69 and #70, open as of July 2026.
- 21st.dev pricing — 21st.dev pricing page: free = 2 component copies/day + 2 MCP searches/day + 100 credits/mo; Community $8/mo billed quarterly.
- Untitled UI MCP — untitledui.com/react/integrations/mcp: v8.0 first-party MCP + CLI to “browse, search, and install components using natural language”; open-source free tier + paid PRO.
- Untitled UI pricing — untitledui.com/pricing, July 2026: one-time licenses (Figma PRO SOLO $139 → BUSINESS $999), lifetime updates.
- Relume MCP — relume.io MCP marketing (2026): “Real components, not hallucinations”; MCP available on paid plans only.
- Relume pricing — relume.io/pricing, 2026 structure: Free (30 components), Design $49/mo, Build $99/mo.
Method: cells were compiled in a July 2026 research pass across vendor sites, docs, pricing pages, the official MCP Registry, GitHub issues and public review threads. Where a vendor's public docs don't state something, the cell reads “not stated” instead of a guess. Mozaika's own cells describe the live product at mozaika.design.
04 · FAQ
Quick answers.
What does “agent-ready” mean for a design library?
That an AI coding agent (Claude Code, Cursor, Codex) can query it mid-build and receive something it can act on. The bar has three parts: an MCP or equivalent API exists; the payload is buildable (measured values or code, not just images to look at); and the terms — free tier, call caps, billing, license — don't break an automated workflow.
Is this scoreboard biased toward Mozaika?
It's written by Mozaika, so read it that way — but every non-obvious cell carries a source note from vendor docs, pricing pages or public reviews, dated July 2026, and Mozaika's own gaps are graded in the open: a far smaller library (~330 web products), no mobile coverage, and a 2026 launch with no long track record.
How were the cells verified — and what if one is wrong?
Cells come from a July 2026 research pass over vendor sites, docs, pricing pages, the official MCP Registry, GitHub issues and public review threads. Where a vendor's docs don't state something, the cell says “not stated” rather than guessing. If you spot an error, it will be corrected — the page is dated so you can hold it to that.
Run the test yourself
The only row that matters is the one your agent confirms.
claude mcp add --transport http mozaika https://mozaika.design/mcp · 25 free calls/mo · no card