Connect Screenrove: UI Design Reference & Screenshots (free Mobbin alternative) and your agent gets 27 tools, among them build_handoff, build_recipe, check_my_ui. It answers at https://screenrove.com/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 29 September 2026; the last check, on 15 November 2026, succeeded.
Real product UI captures (onboarding, pricing, in-app screens) with design guides for coding agents.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
build_handoff | Build one product's reference as a complete prompt: ordered screens with notes, observed transitions, links to up to 10 agent-sized images (1x copies and section crops, each with its pixel size), the measured design guide and an implementat Inputs: referenceId, goal, stack, screens, includeDesign |
build_recipe | The best way to build from references, with or without a person: pass 2 to 6 screen ids from search_screens (each "id: what to take from it") and get one Markdown brief with the screenshots attached at 1x (section crops for long pages), mea Inputs: screens, style, styleContext, styleNotes, goal, stack |
check_my_ui | Compare the user's UI structure with the closest real products. Describe what they have (screen type, sections, flow steps, plan count; no personal names, prices or customer data) and get factual comparisons, not recommendations: plan count Inputs: description, screenType, sections, flowSteps, flowType, primaryAction |
compare_pricing | A fact table of 2 to 8 captured pricing pages, for research rather than building: per product, plan names and prices, cheapest paid plan with currency, monthly/yearly toggle and saving, free plan, trial, seat model, enterprise tier, notable Inputs: screens, products |
compare_screens | Compare two screens side by side (screen types, page sections, observed actions, dimensions, plan counts), e.g. Linear's pricing page with Stripe's, or one screen against a description of what the user is building (targetDescription). Inputs: screenA, screenB, targetDescription, focus |
find_related_screens | Find screens from other products that solve the same design problem as this one: same primary pattern first, then shared tasks, states and components (rarer tags count more). At most two per product; each says why it matched, and a dark-the Inputs: screenId, limit, kind, sameProduct |
get_design | Get a product's measured design guide: fonts, colour palette, type scale, layout and component observations, measured separately for its marketing site and product UI. Use it for "make it look like <product>" or "trustworthy like <product>" Inputs: productId, context |
get_email_flow | One company's onboarding emails in order: strategy, takeaways, and each email's day, stage, sender, subject, preheader and buttons. detail=full adds text; images=N attaches N emails. Inputs: flowId, detail, images |
get_flow | Get a product's captured flow: every step in order with title, notes, page url, observed transitions (button labels and where they lead) and which steps are alternate branches, plus the handoffId for build_handoff. Use it to study how a pro Inputs: productId |
get_motion | Get one motion entry as a build prompt: what moves and how (every property, duration, easing or spring, delay and trigger), why it feels good, how to adapt it to another size, the accessibility it needs, Screenrove's vanilla HTML/CSS/JS and Inputs: motionId, code |
get_motion_guidelines | House rules for UI motion (durations, enter and exit easing, springs, reduced motion) with duration and easing tokens and the library's categories and triggers. Read it once before adding animation. |
get_product | Get one product's collection: what was captured (coverageLabel, coverage, captureNote) and every screen, grouped into flow, marketing and product, one line each (id, title, primary pattern, page url). detail=full adds each screen's notes an Inputs: productId, detail |
get_screen | Get everything recorded about one screen: notes on what it does and how it's laid out, product, captured date, page url, source URL, dimensions, observed actions and where they lead, and page sections for long marketing pages. The notes are Inputs: screenId |
get_screen_image | See the screen; call it on your top picks before writing UI. preview (default) is 1x, so 1 image px = 1 CSS px (the top of a long page). The text gives its pixel size and a long page's sections: section=N returns one as a 1x crop. size=full Inputs: screenId, size, section |
list_email_flows | Real onboarding email sequences from 97 SaaS products (684 emails) after a fresh signup: emails, days, week-one count and stages per flow. Then get_email_flow or search_emails. Inputs: q, stage |
list_flows | List captured user journeys (signup and onboarding, checkout, booking, search, marketplace, and task flows such as building a board) with step counts and flow type, 40 at a time. A flowType marked typeInferred was read from the flow's first Inputs: flowType, offset, limit |
list_products | List the 191 products in the catalog, one compact line each: id, name, category, a one-line coverageLabel saying what was captured (signed in or logged out only), screen counts and page url. Paged (50 by default) and filterable by category Inputs: category, q, detail, offset, limit |
list_tags | List the tag vocabulary for searching by design problem: four facets (task, pattern, component, state), each tag with its definition, aliases and how many screens carry it. Use the ids with search_screens or pick_reference, e.g. pattern=boa Inputs: facet |
name_patterns | How real products are named: pattern shares with examples, TLDs, domain styles, length and syllables, a per-category table and highlights such as the share of AI tools on .ai. Takes search_names' filters for one slice. Use it before proposi Inputs: category, pattern, tld, length, startsWith, source |
pick_reference | Show a person 2 to 6 matching references side by side in their browser and let them click the one to build from. Returns a URL to open for them; then call wait_for_pick with the pickId for their choice and a build prompt. Only when a person Inputs: q, screens, product, kind, task, pattern |
search_emails | One kind of onboarding email across companies, by words, stage, product and send day (e.g. stage=trial-ended). Attaches the top result's image. Inputs: q, stage, product, maxDay, offset |
search_logos | Logo references for designing a logo or app icon: each library product's own mark as its site serves it (never redrawn) with mark type, colours, shape, letter case, brand font and category, e.g. "lettermarks on a rounded tile", "green symbo Inputs: q, product, markType, colour, shape, category |
search_motion | Search the motion library: UI animations and micro-interactions (button presses, toggles, toasts, number tickers, check-offs, thinking states, hover effects, sounds) from open-source libraries and designers' recordings, each with an exact s Inputs: q, category, trigger, source, basis, hasCode |
search_names | Naming ideas grounded in about 700 real product names, each with domain, TLD, category, naming pattern, length, syllables, casing and domain style (getX.com, Xhq.com…), plus stats for the whole match, e.g. "short invented names for AI tools Inputs: q, pattern, tld, category, length, syllables |
search_screens | Find screens by design problem and keyword, e.g. "pricing page like Stripe", "settings", "empty project list". Every screen is tagged on four facets: task, pattern (screen archetype), component and state. Commas mean OR within a facet, face Inputs: q, task, pattern, component, state, scope |
suggest_polish | Given the parts of a UI (elements, a description, or Screenrove screen ids; from a screenshot, list the parts you see), returns motion entries and sounds that would improve each part, plus new touches it doesn't have yet (additions), not on Inputs: elements, description, screens, sources, sound |
wait_for_pick | Wait for the person to choose on the pick page. Long-polls up to 50 seconds and returns as soon as they click, or status "pending" (call again). Once chosen: their reference with its screenshot attached and a full build prompt. "dismissed" Inputs: pickId, wait |
Every block below points at https://screenrove.com/mcp. Pick your client and copy.
claude mcp add --transport http screenrove-ui-design-reference-s https://screenrove.com/mcp
{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://screenrove.com/mcp"]
}
}
}{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"url": "https://screenrove.com/mcp"
}
}
}{
"servers": {
"screenrove-ui-design-reference-s": {
"type": "http",
"url": "https://screenrove.com/mcp"
}
}
}{
"context_servers": {
"screenrove-ui-design-reference-s": {
"url": "https://screenrove.com/mcp"
}
}
}{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"serverUrl": "https://screenrove.com/mcp"
}
}
}{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"url": "https://screenrove.com/mcp"
}
}
}name: Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)
version: 0.0.1
schema: v1
mcpServers:
- name: Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)
type: streamable-http
url: https://screenrove.com/mcp{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"httpUrl": "https://screenrove.com/mcp"
}
}
}{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"type": "http",
"url": "https://screenrove.com/mcp"
}
}
}{
"mcpServers": {
"screenrove-ui-design-reference-s": {
"url": "https://screenrove.com/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fscreenrove.com%2Fmcp&type=streamable_http&id=screenrove-ui-design-reference-s&name=Screenrove%3A%20UI%20Design%20Reference%20%26%20Screenshots%20%28free%20Mobbin%20alternative%29
It answered our last check on 15 November 2026 in 1209 ms. Over 4 checks since 29 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by screenrove.com and served from screenrove.com, the vendor's own domain: https://screenrove.com/mcp.
27, as returned by the server's own tools/list on 18 November 2026: build_handoff, build_recipe, check_my_ui, compare_pricing, compare_screens, find_related_screens, get_design, get_email_flow, and 19 more.
It answered our last check on 15 November 2026 in 1209 ms. Over 4 checks since 29 September 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://screenrove.com/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.screenrove. Endpoint host: screenrove.com. ARD identifier: urn:air:com.screenrove:mcp:screenrove.
First indexed 29 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.