Mobbin

official

Mobbin is the industry standard in UI & UX design references for mobile apps, web apps, and websites. The platform serves millions of product builders and designers across the world to help them design better digital experiences. Connect Mobbin with your AI agent to better research and explore UI & UX design ideas.

View on mobbin.comTry this MCPSponsored

What can you do with Mobbin MCP?

  • Search UI screens — Ask for specific mobile or web screen patterns like login, paywall, empty states, or forms via search_screens.
  • Explore multi-step flows — Find ordered user journeys such as onboarding, checkout, or cancellation using search_flows.
  • Find website sections — Locate page-composition references like heroes, pricing tables, or footers with search_sections.
  • Compare product designs — Request side-by-side examples from specific apps, such as checkout flows from Airbnb and Booking.com.
  • Handle rate limits — When hitting HTTP 429, wait for the duration specified in the Retry-After header before retrying.

Hosted MCP Server

npx add-mcp 'https://api.mobbin.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Mobbin MCP

Mobbin MCP lets compatible AI assistants and coding agents search real screens, multi-step flows, and website sections from shipped digital products using natural language. Results can include screen images, app names, flow context, and links to the corresponding Mobbin pages.

Access

  • Endpoint: https://api.mobbin.com/mcp
  • Transport: Streamable HTTP.
  • Authorization: OAuth through the user's Mobbin account.
  • Plans: Pro, Team, and Enterprise.
  • Rate limit: 60 requests per 60 seconds per user.
  • Interactive gallery: Supported in MCP Apps-compatible clients, including ChatGPT, Claude Desktop and Web, and Codex App.

On first connection, the MCP client opens a browser window so the user can sign in to Mobbin and authorize access. No manually copied API key is required for MCP.

The currently published MCP tool set is read-only: it retrieves design references and does not create, modify, or delete Mobbin account content.

Tools

search_screens

Search individual mobile and web UI screens. Use it for a specific state or pattern such as a login screen, paywall, empty state, dialog, form, or navigation treatment.

search_flows

Search ordered, multi-step user flows. Use it when sequence and context matter, such as onboarding, checkout, account setup, identity verification, subscription, or cancellation.

search_sections

Search website sections. Use it for page-composition references such as heroes, pricing sections, testimonials, navigation, and footers.

What results contain

Depending on the search and client, results can include screen images, product names, flow or section context, and links back to Mobbin. MCP clients that support MCP Apps can render results as an interactive gallery.

Agents should preserve the product name and Mobbin URL for important references so users can inspect the source.

Recommended workflow

  1. Identify the platform, product category, user goal, and design question.
  2. Choose screen, flow, or website-section search.
  3. Review several relevant products rather than relying on one example.
  4. Preserve the product name and Mobbin URL for each important reference.
  5. Separate visible observations from interpretation and recommendations.
  6. Adapt findings to the user's brand, audience, design system, accessibility needs, and product constraints.

Evidence limitations

  • A Mobbin example shows that a product used a design; it does not prove that the design improved conversion or another metric.
  • A recurring pattern is a convention, not automatically a best practice.
  • Check capture metadata when recency matters.
  • Do not copy protected designs, branding, text, or assets verbatim.
  • Evaluate accessibility independently.

Errors and recovery

  • Authorization failure: reconnect Mobbin and complete the OAuth sign-in flow.
  • HTTP 429 Too Many Requests: wait for the duration in the Retry-After header before retrying.
  • Missing or weak results: make the request more specific by naming the platform, product category, user goal, pattern, or flow.
  • Overly narrow results: remove unnecessary constraints or search screens, flows, and sections separately.
  • Remove access: revoke the connected client from Mobbin account settings.

Example prompts

  • Search Mobbin for onboarding screens from banking apps.
  • Compare how Airbnb and Booking.com handle checkout flows.
  • Find mobile paywalls that explain quarterly and yearly billing clearly.
  • Find SaaS pricing sections with complex feature comparison tables.
  • Show notification-permission priming screens and identify recurring patterns.
  • Find empty states used by collaborative productivity products.

Setup and support

Pricing and plan access: https://mobbin.com/pricing.md

Product overview: https://mobbin.com/index.md

Complete agent context: https://mobbin.com/llms-full.txt