Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)
v1.9.0Real SaaS UI screenshots for coding agents: onboarding flows, pricing pages, design inspiration.
Endpoint health
online- Last checked
- 11/20/2026, 9:16:44 AM
- Latency
- 2454 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.screenrove%2Fscreenrove
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.screenrove/screenrove": {
"url": "https://screenrove.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
Build an agent handoff prompt
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 implementation checklist; the same prompt as the site's "Use in agent" button. referenceId is `{product}-onboarding` (its flow), `{product}-collection` (everything) or one screen id. To combine screens from several products, use build_recipe.
Schema valid · SHA-256 6c9281b29790…
View input schema
{ "type": "object", "properties": { "referenceId": { "type": "string", "description": "e.g. linear-onboarding, stripe-collection or vercel-marketing-pricing." }, "goal": { "type": "string", "description": "What you want to build. Goes at the top of the prompt." }, "stack": { "type": "string", "description": "Preferred stack, e.g. Next.js and Tailwind." }, "screens": { "type": "string", "description": "Comma-separated screen ids to keep. Omit to include every screen in the reference." }, "includeDesign": { "type": "boolean", "description": "Include the observed design guide. Set false to use your project's own design system.", "default": true } }, "required": [ "referenceId" ], "additionalProperties": false }Build a reference recipe
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), measured component sizes, the page structure and what to take from each. Up to 6 images are attached (one per reference, then extra section crops); the brief's first line lists them and names a get_screen_image call for any left out. Structure comes from the screens and every visual token from one style product, so conflicting looks are resolved instead of mixed. Interactive parts get matching motion entries to fetch with get_motion. E.g. Linear's issue composer, Vercel's pricing layout and Notion's look in one screen.
Connections
streamable-http
https://screenrove.com/mcp