Mobbin

Tools 8

• Search Screens

  Search 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. Inline images are low-res previews for you to read, not for the user. Each result's `image_url` is the high-resolution image. Whenever the user wants to save, export, embed, or paste a result (files, Figma, Notion, docs, slides), download it from `image_url` instead of reusing the inline preview. Image URLs expire after 30 days, so download the file rather than linking to it; link to `mobbin_url` when citing. On hosts that support MCP Apps, also renders an interactive gallery of the results.

• Search Flows

  Search 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. Inline images are low-res previews for you to read, not for the user. Each result's `image_url` is the high-resolution image. Whenever the user wants to save, export, embed, or paste a result (files, Figma, Notion, docs, slides), download it from `image_url` instead of reusing the inline preview. Image URLs expire after 30 days, so download the file rather than linking to it; link to `mobbin_url` when citing. On hosts that support MCP Apps, also renders an interactive gallery of the results.

• Search Sections

  Search 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. Inline images are low-res previews for you to read, not for the user. Each result's `image_url` is the high-resolution image. Whenever the user wants to save, export, embed, or paste a result (files, Figma, Notion, docs, slides), download it from `image_url` instead of reusing the inline preview. Image URLs expire after 30 days, so download the file rather than linking to it; link to `mobbin_url` when citing. On hosts that support MCP Apps, also renders an interactive gallery of the results.

• List Collections

  List what's saved for the user's Mobbin MCP connection: All saved, then each collection, most recently changed first. Each entry counts the iOS screens, iOS flows, web screens, web flows and website sections the user can see, and links to it on Mobbin. A count of zero means there is nothing of that kind to fetch: tell the user instead of fetching. Use it when the user refers to their saved screens, flows or sections, or to a collection by name. Collection names are not unique. Before fetching from a collection the user named, check whether more than one entry has that name; if so, stop and ask the user which one they mean, telling them apart by `updated_at` or by what each holds. A private collection's `mobbin_url` opens only for the user and their teammates; say so when you give one out.

• Get Collection Contents

  Fetch one page of the items saved in a collection, or in everything the user saved: iOS screens, iOS flows, web screens, web flows or website sections, one kind per call. `id` is a collection id from list_collections, the UUID at the end of a Mobbin collection URL (https://mobbin.com/collections/<id>), or `all-saved` for everything saved for the user's Mobbin MCP connection. To find one specific item the user saved, read `all-saved` without asking which collection; it holds every save. Items come newest save first. `collection.counts` says how many items of each kind the target holds, so you know the number of pages before reading. Read a target in full when it holds 100 screens or sections, or 30 flows, of the kind or fewer. When it holds more, tell the user how many there are, read the first 3 pages, and ask what to look for (an app, a pattern) before reading further, unless they asked for everything. A page can hold fewer than `limit` items and still have a next page. You can read at most 20 pages of a kind. Older saves past that cannot be fetched here. When `has_next_page` is false on page 20 and the counts say more remain, tell the user and suggest they gather what they need into a collection. Each item carries the user's team's `comments` on it, oldest first. Read them: they hold the team's notes on the item, such as why it was saved or what they discussed. Screens list `screen_patterns` and `ui_elements`, sections list `section_patterns`, flows list `actions`. Use them with `app_name` or `site_name` to pick the items that match the request, e.g. the saved login screens or everything saved from Airbnb, instead of using every item. Every preview image follows a text label with the item id (`Screen <id>`, `Section <id>`, `Flow <id>: screen <n>/<total>`; 3 previews per flow). Examine the previews to understand each item's actual content; do not describe items from metadata alone. Inline images are low-res previews for you to read, not for the user. Each result's `image_url` is the high-resolution image. Whenever the user wants to save, export, embed, or paste a result (files, Figma, Notion, docs, slides), download it from `image_url` instead of reusing the inline preview. Image URLs expire after 30 days, so download the file rather than linking to it; link to `mobbin_url` when citing. When you present items, cite each one as a markdown link to its `mobbin_url`.

• Create Collection

  Create a collection for the user's Mobbin MCP connection, and return its id and link. It starts empty: call save_content with the returned id to add screens, flows or sections. It is private: only the user and their teammates can open the link, and say so when you give it out. The user can make it public on mobbin.com. Use it when the user asks for a new collection, or wants to save into one that list_collections does not have. Collection names are not unique, so check list_collections first when the user may already have one with that name.

• Save Content

  Save screens, flows or website sections for the user's Mobbin MCP connection. Pass `collection_id: "all-saved"` to save to All saved, or a collection id from list_collections or create_collection to save to that collection, which also saves to All saved. Only the user and their teammates see saved items, unless that collection is public. Use ids from another Mobbin tool's result, like search or get_collection_contents, or the ids (UUIDs) in Mobbin links the user shares. Never guess or make up an id. Use it only when the user asks to save, keep or collect items, never to remember results for yourself. An item already saved there is left as it is. All or nothing: on an error nothing is saved. Fix what the error names and send the same request again, which is always safe.

• Add Comment

  Add a comment to a screen, flow or website section for the user's Mobbin MCP connection, such as why the user saved it. The user and their teammates see it on Mobbin, and get_collection_contents returns it. Use an id from another Mobbin tool's result, like search or get_collection_contents, or the id (a UUID) in a Mobbin link the user shares. Never guess or make up an id. Use it only when the user asks to comment on or add a note to an item. An item that isn't saved yet is saved to All saved first. Mobbin adds a line saying which app posted the comment, so don't sign it. Each call posts a new comment, so send each note once. @mentions aren't supported. If the user wants to mention a teammate, tell them first that no one will be notified and the mention stays plain text.