- Category: images & design
- Auth: DCR_OAUTH
- Composio-managed OAuth available? No
- Tools: 3
- Triggers: 0
- Slug:
MOBBIN_MCP - Version: 20261018_00
Tools
Search flows
Search flows
Slug:
MOBBIN_MCP_SEARCH_FLOWSSearch Mobbin for multi-step user flows (e.g. onboarding, checkout) using natural language. Returns evenly-spaced preview images inline along with metadata for each flow, including per-screen previews. Examine the returned images to understand each flow’s actual content — do not describe screens based solely on metadata. On hosts that support MCP Apps, also renders an interactive gallery of the results.Input Parameters
Describe one user journey in plain language — the steps and what you’d see along the way. Be specific; detail helps. Good: “onboarding with personalization steps”, “checkout with payment method selection”. Avoid: combining multiple flows (search separately), negations, vague style words, disconnected keyword lists. Name a specific app to filter results to it (e.g. “Duolingo onboarding”). Do not include platform (ios/web) — use the dedicated parameter.
One short sentence summarizing the user’s overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.
Output
Search screens
Search screens
Slug:
MOBBIN_MCP_SEARCH_SCREENSSearch Mobbin for UI screens using natural language. Returns matching screens with inline images and metadata. Examine the returned images to understand each screen’s actual content — do not describe or summarize screens based solely on metadata. Each screen has a mobbin_url — the canonical Mobbin link for that screen. When you present results to the user, ALWAYS cite each screen you mention as a markdown link to its mobbin_url so the user can open it on Mobbin. On hosts that support MCP Apps, also renders an interactive gallery of the results.Input Parameters
Search mode. “standard” returns results with low latency. “deep” uses an AI-powered pipeline that interprets intent and scores each candidate for relevance, keeping the strong matches — ideal for nuanced queries. “fast” is a deprecated alias for “standard” and will be removed in a future version — use “standard” instead.
Maximum number of screens to return. Higher number of screens returned causes increased context usage.
Describe one screen in plain language — the UI elements you’d see and how they relate. Be specific; detail helps. Good: “login screen with biometric authentication”, “checkout page with promo code field and Apple Pay button”. Avoid: combining multiple screens/intents (search separately), negations (“without ads”), vague style words (“modern”, “clean”), disconnected keyword lists. Name a specific app to filter results to it (e.g. “Spotify now-playing screen”). Do not include platform (ios/web) — use the dedicated parameter.
One short sentence summarizing the user’s overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.
Output
Search sections
Search sections
Slug:
MOBBIN_MCP_SEARCH_SECTIONSSearch Mobbin for website sections (e.g. About, Pricing, Footer) using natural language. Returns section images inline along with metadata. Examine the returned images to understand each section’s actual content — do not describe or summarize sections based solely on metadata. On hosts that support MCP Apps, also renders an interactive gallery of the results.Input Parameters
Maximum number of sections to return. Higher number of sections returned causes increased context usage.
Describe one website section in plain language — the content and elements you’d see. Be specific; detail helps. Good: “pricing page with plan comparison table”, “hero section with signup form”. Avoid: combining multiple sections (search separately), negations, vague style words, disconnected keyword lists.
One short sentence summarizing the user’s overall task. Helps return more relevant results. Write it in English even when the conversation is in another language. MUST be the same across all calls for the same task. Do NOT include verbatim user messages, conversation history, file contents, or personal data.