Mobbin MCP (real-world design inspiration for recipes)
A built-in MCP integration that connects Claude to Mobbin — a searchable library of real-world app screenshots, user flows and UI patterns — so recipes that ask for design inspiration pull from shipped apps rather than from the model's imagination. Off by default; set up from a card in Settings → Sessions.
On this page
What it is
What it is — Mobbin MCP connects Claude to Mobbin
Mobbin MCP connects Claude to Mobbin — a searchable library of real-world app screenshots, user flows, and UI patterns from thousands of shipped apps. When it's enabled, recipes that ask for design inspiration (chiefly the bundled Design Overhaul recipe) can have Claude search Mobbin for screens, flows, and popular apps in your project's domain and feed what it finds into the design work, instead of inventing an aesthetic from scratch.
"MCP" is the Model Context Protocol — an open standard that lets Claude call out to external tools and data sources. Enabling Mobbin MCP registers a Mobbin MCP server with the Claude Code CLI so any session a recipe spawns can call the Mobbin search tools. It's off by default and requires a one-time authentication: you paste your mobbin.com browser cookie once so Claude can search the library as you.
It works with free and Pro Mobbin accounts. Free accounts are limited to the 4 most recent apps, 3 collections, and basic search; Pro ($10/mo) unlocks the full library, unlimited collections, and advanced filters. There is no Omniscio-side paywall — whatever your Mobbin account can see, the tools can see.
Where to find it
Settings → Sessions, on the Mobbin MCP (design research) card. The card carries the toggle, a Compare plans link and the Setup MCP action.
How it behaves
How to use it
- Open the setting. Go to Settings → Sessions and find the Mobbin MCP (design research) card. The toggle is off by default. The card explains the free-vs-Pro limits with a Compare plans link to
https://mobbin.com/pricing. - Click "Setup Mobbin MCP". Omniscio registers the Mobbin MCP server with the Claude Code CLI in the background — no terminal window opens and no Claude session is spawned. The button shows Setting up… while it works.
- Paste your Mobbin cookie when prompted. If you're not already authenticated, the card switches to a Paste your Mobbin cookie step with four instructions:
- Log into mobbin.com in your browser.
- Open the browser console — press F12 then click the Console tab (or try Ctrl+Shift+J / Cmd+Option+J).
- Run
copy(document.cookie)— nothing visible happens, but the cookie is copied to your clipboard. - Paste it into the box and click Authenticate.
- Confirmation. On success the card shows "Mobbin MCP configured and authenticated." and the toggle flips on. If the cookie isn't accepted you'll see "Cookie not accepted. Make sure you copied the full cookie from mobbin.com." and can retry; if MCP registration itself fails you'll see a hint that the Claude Code CLI must be installed.
- Run a recipe that uses it. The bundled Design Overhaul recipe has a first step, "Gather Mobbin design inspiration," that calls the Mobbin tools (
mobbin_search_screens,mobbin_search_flows,mobbin_popular_apps,mobbin_quick_search,mobbin_get_app_screens) to build a design-inspiration brief before auditing your project. That step is written to skip gracefully if the tools aren't available — the overhaul still runs without Mobbin, just without the real-world reference brief. - Turn it off any time by flipping the toggle back off. The cookie you pasted lives on your machine (see below), not in Omniscio's database.
You only authenticate once. The pasted cookie is parsed for your Mobbin session token and stored locally; you don't need to repeat the steps unless the token expires or you sign out of Mobbin.
Related
Related — use-recipes.md
- use-recipes.md — recipes (including Design Overhaul) are what consume the Mobbin tools
- mempalace-memory.md — the other built-in MCP integration Omniscio wires into sessions
Last verified 2026-10-06