Duply
Launch Kit
Back to blog

9 September 2026

Mobbin MCP: what it gives your AI agent, and what it can't

Mobbin shipped an MCP server in May 2026 and search demand for it went from roughly 40 a month to 3,600 a month by summer. Worth understanding before you pay for it.

Quick answer: Mobbin MCP is an official Model Context Protocol server that lets an AI agent search Mobbin's library of real, shipped product screens from inside your coding tool. Your agent gets image URLs, app names and links back to Mobbin, returned inline in the conversation. It requires a paid Mobbin plan, runs over Streamable HTTP with OAuth, and is capped at 60 requests per 60 seconds. It solves the reference problem, not the consistency problem: it shows your agent what good looks like, but it does not hand over the token values, scales or rules that keep your own interface coherent across 40 screens.

What Mobbin MCP actually is

Mobbin is a subscription library of screenshots and recorded user flows captured from real iOS, Android and web products. Until May 2026 you browsed it in a tab. The MCP server makes the same library callable by an agent.

Mobbin's own MCP page puts it as: "Mobbin MCP connects your AI agents to 600,000+ real product screens, so what they build starts with what already works." The Business Wire release dated 12 May 2026 puts numbers on the library at launch: 621,500+ screens and 142,200+ flows, with Claude, Cursor and Lovable named as supported clients. Mobbin CEO Jiho Lim is quoted in that release: "Mobbin MCP gives AI agents access to real design decisions, patterns, and flows, not generated guesses."

Google's AI Overview for the query now summarises it as "an official Model Context Protocol server that connects AI coding assistants like Claude Code and Claude Desktop to Mobbin's library of over 600,000 real-world product screens and UI flows."

The adoption numbers are not small. Mobbin's own write-up on how to use Mobbin MCP opens by saying "We tracked 317427 queries from 10105 Mobbin MCP users."

What the server actually exposes

Three tools, per Mobbin's MCP features docs:

  1. search_screens which "Searches UI screens."
  2. search_flows which "Searches multi-step user flows such as onboarding and checkout."
  3. search_sections which "Searches website sections such as pricing pages and footers."

The API reference describes the underlying call plainly: "Search Mobbin for screens using natural language. Returns relevant screens with image URLs, app names, and links to Mobbin." The introduction page adds that the server "returns screen images inline for AI consumption in its tool responses."

In clients that support the MCP Apps specification, including ChatGPT, Claude Desktop and Web, and the Codex app, the server "renders an interactive gallery of search results inline in the conversation" instead of a wall of URLs.

The important detail for anyone planning a workflow around it: what comes back is imagery plus metadata. Screens, flows, sections, app names, links. Not a stylesheet, not variables, not written rules.

What it structurally cannot give an agent

This is the part the setup tutorials skip, and it is not a criticism of Mobbin. It is a property of the format.

A screenshot of Linear's issue list tells your agent what the row height looks like. It does not tell it that the row height is 32px, that it comes from a 4px spacing scale, that the muted text is one specific token and not a hand-picked grey, or that the same token has to be used on the 39 other screens your agent has not built yet.

So an agent with Mobbin MCP will produce a better first screen. What it will not produce, on its own, is the twentieth screen matching the first. That failure mode has its own well-worn Reddit literature, covered in why AI-generated apps all look the same.

Reference material and specification are two different inputs:

Mobbin MCPA DESIGN.md
Gives the agentReal screens, flows, sectionsToken values, scales, component rules
Answers"How do good apps do this?""What are the exact values for this project?"
FormatImages plus metadataText the agent reads on every task
Consistency across screensNot enforcedEnforced by re-reading the same file

They compose. Research the pattern, then constrain the implementation.

Setup: Claude Code, Cursor, and the rest

Mobbin documents 23 clients, including Claude Code CLI, Claude Desktop and Web, Claude Design, ChatGPT, Codex CLI and app, Cursor, VS Code, GitHub Copilot CLI, Figma agent and Figma Make, Lovable, Replit, v0, Devin, Manus, Magic Patterns and Antigravity. The full list is in Mobbin's client docs.

For Claude Code, the command reproduced in Google's AI Overview and in DesignerUp's walkthrough from 14 May 2026 is:

claude mcp add --transport http mobbin https://api.mobbin.com/mcp

Then start Claude Code, run /mcp, and authenticate in the browser window it opens. Mobbin's docs confirm the mechanism: the server "uses the Streamable HTTP transport" and "authorizes via OAuth." Evangeline Ng's Substack guide states the prerequisite bluntly: "A paid Mobbin account. The MCP works by authenticating with your session."

For desktop clients there is no terminal step. As one YouTube walkthrough from July 2026 describes it: "If you go to Mobin and go to your settings, you'll now find a new MCP tab there." Mobbin is also listed as a verified connector in Claude's directory.

Rate limits, from Mobbin's own docs: 60 requests per 60 seconds per user for MCP, 60 per 60 seconds per workspace for the REST API. Exceed it and you get a 429 with a Retry-After header. That is generous for interactive design work and tight for anything batch.

What it costs, and the credits change

Access is plan-gated, and the gate has moved since launch.

  • The May 2026 press release said the MCP server was "Available now on all paid plans," in beta.
  • Mobbin's current docs say: "The Mobbin MCP server is available on Pro, Team, and Enterprise plans."
  • A Medium write-up from roughly July 2026 reports "Mobbin's entry plan is $15/month, quarterly, or $10/month annually. The MCP is included in every paid tier. Free tier doesn't include it."
  • Mobbin's pricing page currently advertises "From a low cost of $2.50/week, get unlimited access to product design references."

There is also a live change worth knowing about before you buy an annual plan. An r/ClaudeCode thread posted in late August 2026 quotes a Mobbin notice: "Starting Monday, September 14, AI-powered features on Mobbin will run on credits. Your plan includes credits at no extra cost. They reset ..." The poster's own question is the honest summary of where things stand: "Anyone have a greater understanding of the Mobbin Change? I signed up for a 1 year plan with Mobbin as a lot of YouTubers use Clau..."

We could not verify the credit allowances on Mobbin's own pages at time of writing, so treat the pricing page as the only authority and check it before committing to an annual plan. Every figure above is as of 9 September 2026.

What people report using it for

Verbatim from live Google results, so you can judge the source yourself:

Using it well

✅ Do this:

  • Ask for a pattern, not a picture. "Research how five shipped fintech apps structure their transaction detail screen, then summarise the shared structure" beats "make me a transaction screen."
  • Run it as a discovery step before implementation, then write down what you learned as project rules.
  • Use search_flows for multi-step work (onboarding, checkout, permissions). That is the part a screenshot library gives you that a general model cannot invent.
  • Check the credit and plan terms before buying annually, given the September 2026 change.

❌ Avoid this:

  • Expecting reference imagery to make your output consistent. It will not. Nothing in a screenshot binds your agent to the same spacing scale next Tuesday.
  • Firing dozens of searches per task. You have 60 requests per minute, and every extra image is context your agent spends not writing code.
  • Treating "looks like Stripe" as a specification. Your agent will approximate it differently every time.

The workflow that actually holds up

Two inputs, two jobs.

  1. Reference. Mobbin MCP answers "how do good products solve this screen." Use it at the start of a feature.
  2. Specification. A DESIGN.md file answers "what are the exact values and rules for this project." Your agent reads it on every task, so screen 40 matches screen 1.

Browse the duply library for real systems written in that format, look at a full example such as Linear, Stripe or Vercel, and follow how to give your AI agent a real design system to wire it into the same agent you just connected Mobbin to.

FAQ

What is Mobbin MCP? An official Model Context Protocol server, launched 12 May 2026, that lets AI coding agents and chat apps search Mobbin's library of real shipped product screens using natural language. It returns screen images, app names and links inline in the conversation.

Is Mobbin MCP free? No. It requires a paid Mobbin plan. Mobbin's current docs say the server is available on Pro, Team and Enterprise plans, while the launch press release said all paid plans. The free tier does not include it.

How do I add Mobbin MCP to Claude Code? Run claude mcp add --transport http mobbin https://api.mobbin.com/mcp, start Claude Code, then run /mcp and complete the OAuth sign-in in the browser window it opens. Desktop and web clients connect through the MCP tab in Mobbin's settings instead.

What tools does the Mobbin MCP server expose? Three: search_screens for UI screens, search_flows for multi-step user flows such as onboarding and checkout, and search_sections for website sections such as pricing pages and footers.

Are there rate limits? Yes. Mobbin's docs list 60 requests per 60 seconds per user for MCP and 60 per 60 seconds per workspace for the REST API, returning HTTP 429 with a Retry-After header when exceeded.

Is Mobbin MCP worth it? If you already pay for Mobbin and use an AI coding agent, it removes the copy-paste step and is an easy yes. If you are buying Mobbin specifically for the MCP, understand what you are buying: better reference input, not consistent output. Budget for the specification layer separately.

Does Mobbin MCP fix AI-generated designs looking generic? Partially. It replaces the model's average-of-the-internet defaults with real shipped patterns, which helps a lot on any single screen. It does not enforce consistency across a whole app, because images carry no token values or rules. That needs a written spec.

Is there an unofficial Mobbin MCP server? Yes, pdcolandrea/mobbin-mcp on GitHub, published May 2026. It is community-maintained and unsupported by Mobbin, so expect it to break when the platform changes.

What can Mobbin MCP not do? It cannot give your agent design tokens, type or spacing scales, component rules, or accessibility constraints, because none of those are in a screenshot. It also cannot make two separately generated screens agree with each other.

Summary

  • Mobbin MCP is an official MCP server, live since 12 May 2026, exposing 621,500+ screens and 142,200+ flows to AI agents
  • Three tools: search_screens, search_flows, search_sections, returning images, app names and links inline
  • Setup is one command for Claude Code, or the MCP tab in Mobbin settings for desktop and web clients, with OAuth over Streamable HTTP
  • Paid plans only, 60 requests per 60 seconds, and AI features move to a credit system on 14 September 2026 per a notice quoted on Reddit
  • Reddit's verdict so far: genuinely useful, immediately habit-forming, still considered expensive
  • It fixes your agent's reference problem. It does not fix consistency, which needs a DESIGN.md your agent reads on every task

Give your agent both. Start with the duply library.

Related reading