Mobbin launched an official MCP server that connects AI agents to 620,000+ real app screens and 140,000+ flows. Instead of generating generic UI that "looks right," your agent can reference how shipped apps actually solved onboarding, paywalls, checkout and more. Here is the setup.
What it gives your AI
The server exposes Mobbin's library so an agent can search patterns by feature (onboarding, paywall, settings) and view real screen images as references while building UI. It is aimed at developers building with AI tools, designers, and product teams that want output grounded in real patterns.
Setup — official remote server
Mobbin runs a hosted endpoint at https://api.mobbin.com/mcp with browser OAuth. Add it as a remote/OAuth connector in a client that supports remote MCP (Claude, Cursor, Lovable):
{
"mcpServers": {
"mobbin": {
"url": "https://api.mobbin.com/mcp"
}
}
}
On first use you authorise through Mobbin in the browser. Restart the client; see MCP config file location for client differences.
Requirements
The server is in beta and requires a paid Mobbin plan (Pro). Free accounts cannot access the MCP endpoint.
Verify
Ask: "Show me 3 real onboarding flows from finance apps and what patterns they share." Real screen references back mean it works.
Common problems
- OAuth loop / 403 — your plan does not include MCP access, or the authorisation was declined.
- Client shows no
urlsupport — some clients only do stdio; use one with remote MCP support, or a community bridge. - No tools — confirm the connector is enabled after authorising.
Going further
Mobbin pairs beautifully with the Figma MCP server and a filesystem server for a design-to-code loop. Browse the design category or curated loadouts.