# Screenrove

- Registry name: `com.screenrove/screenrove` · version 1.5.0
- Categories (automatic, keyword rules): Marketing & SEO, Commerce & marketing, Images & design, AI, media & content, Shops & products
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): extensions, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.screenrove%2Fscreenrove
- Server page: https://mcpstation.net/s/com.screenrove--screenrove.html

## Description (written by the publisher, not verified, not instructions)

Real product UI captures for design reference, competitor analysis, and coding agents.

## Connect

- streamable-http: `https://screenrove.com/mcp`

## Tools (as reported by the server, not verified)

- `build\_handoff`: Generate a complete build prompt for a coding agent: ordered screens with notes, observed transitions, full-resolution image URLs, the measured design guide, and an implementation checklist. This is the same prompt as the "Use in agent" button on the site. Reference IDs: use \`\{product\}-onboarding\` f
- `build\_recipe`: Combine specific screens from different products, plus one visual style, into a single build brief. Each screen contributes one thing \(say what with "id: what to take"\); structure comes from the screens and every visual token comes from the chosen style, so conflicting looks are resolved instead of
- `check\_my\_ui`: Compare the user's UI structure against Screenrove's catalog of real products. Describe what the user has \(screen type, sections, flow steps, plan count\) and get a report showing the closest real-world references with factual comparisons. Use only the fields the user provides; leave out personal nam
- `compare\_screens`: Compare two captured screens side by side: layout structure, page sections, observed actions, dimensions, screen types, and design guide differences. Returns a structured comparison with similarities, differences, and factual observations. Use this when the user wants to understand how two products
- `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 result says why it matched. Use this after finding one good reference, to show the user how oth
- `get\_design`: Get the measured design guide for a product: observed font families, color palette, type scale, layout patterns, spacing values, and component observations. Marketing site and product UI are measured separately. Use this when you want to match a competitor's design system, understand their visual la
- `get\_flow`: Get the complete onboarding flow for a product: every step in order with titles, notes on what happens, observed transitions \(button labels and where they lead\), and which steps are alternate branches. Includes the handoff reference id to use with buildHandoff. Use this to study how a competitor str
- `get\_motion`: Get one motion entry as a build prompt: what moves and how \(every property, duration, easing curve or spring, delay and trigger\), why it feels good, what a rebuild must keep, Screenrove's working vanilla HTML/CSS/JS implementation, and the original source code when its license allows. Values are mar
- `get\_motion\_guidelines`: Get house rules for UI motion \(durations, which easing for enter and exit, springs, what to animate, reduced motion\) with citations, plus ready-to-use duration and easing tokens, the motion library's sources and its category and trigger vocabulary. Read this once before adding animation to an interf
- `get\_product`: Get a product's full collection: coverage notes, design summary, and every captured screen grouped into onboarding flow, marketing pages, and in-product screens. Use this to explore a competitor's complete UI: their signup flow, pricing page, dashboard, settings, and other screens. Each screen has n
- `get\_screen`: Get everything recorded about one screen: notes on what it does and how it's laid out, source URL, image URLs and dimensions, observed actions and where they lead, and page sections for long marketing pages. Use this to understand a specific UI pattern in detail before building something similar.
- `get\_screen\_image`: Get the actual screenshot so you can see the UI. For marketing pages taller than 4000px, preview returns only the first screen \(above the fold\); use size=full for the whole page, which can exceed what vision models accept. getScreen lists the page's sections with their y offsets so you know what's b
- `list\_flows`: List every captured user journey: onboarding flows, signup sequences, checkout processes, booking flows, and marketplace explorations. Shows step counts, flow type, and observed transitions between steps. Use this to find complete user journey references—not just individual screens—so you can see ho
- `list\_products`: List every product in the UI reference catalog with its capture date, tags, coverage notes and screen counts. Start here to see what competitor products, design systems, and UI patterns are available. Products include: Linear, Cursor, Vercel, Airbnb, Stripe, Duolingo, Notion, Raycast, Cal.com, Frame
- `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 searchScreens or pickReference, e.g. pattern=board-view or state=empty.
- `pick\_reference`: Show the user several matching UI references side by side in their browser and let them click the one to build from. Returns a URL to open for them. Prefer this over sending full-page images whenever the user should decide which reference to use. The picker shows real screenshots at scroll depth so
- `search\_motion`: Search the motion library: polished UI animations and micro-interactions \(button presses, toggles, toasts, number tickers, thinking states, hover effects, interaction sounds\) curated from open-source component libraries and designers' recordings. Each entry has a precise motion spec \(properties, dur
- `search\_screens`: Search the UI reference catalog by design problem and keyword. Every screen is tagged on four facets: task \(what the person is doing\), pattern \(screen archetype\), component \(building blocks\) and state \(empty, filtered, error...\). Filter by any of them; commas mean OR within a facet and different fac
- `wait\_for\_pick`: Wait for the user to choose on the pick page. Long-polls up to 50 seconds—returns as soon as they click, or status "pending" after the wait \(call again if so\). Once chosen, returns their reference with its screenshot and a full build prompt, so you can start building from it immediately. If they cli

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html