MCP Server
Screenrove
com.screenrove/screenrove
What this MCP does
Provides captured product screens, screenshots, measured design guides, UI comparisons, and implementation handoff prompts.
Capabilities
Tools
13
tools
build_handoff
Build an agent handoff prompt
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` for a product's signup flow, `{product}-collection`
for all their screens, or any single screen id (like `linear-marketing-pricing`).
Use this when you want to build UI that follows a real product's patterns. The prompt includes
everything an agent needs: screenshots to reference, design tokens to match, and implementation
steps to follow.
Read only
Input schema
{'type': 'object', 'required': ['referenceId'], 'properties': {'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.'}, 'referenceId': {'type': 'string', 'description': 'e.g. linear-onboarding, stripe-collection or vercel-marketing-pricing.'}, 'includeDesign': {'type': 'boolean', 'default': True, 'description': "Include the observed design guide. Set false to use your project's own design system."}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'prompt': {'type': 'string', 'description': 'Markdown prompt to follow or paste into an agent.'}, 'manifest': {'type': 'object', 'description': 'Versioned reference manifest'}}}
check_my_ui
Check the user's UI against real references
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 names, pricing, or customer data.
The report includes step counts, section counts, observed actions, and factual comparisons—
not recommendations.
Use this when the user wants to validate their UI against real products, understand if their
flow has more or fewer steps than competitors, or see how similar screens are structured.
Read only
Input schema
{'type': 'object', 'required': ['description'], 'properties': {'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'Only compare with this kind of capture.'}, 'limit': {'type': 'number', 'default': 4, 'description': 'How many references to return, 1 to 5.'}, 'product': {'type': 'string', 'description': 'Only compare with this product id.'}, 'flowType': {'enum': ['signup-onboarding', 'search', 'checkout', 'booking', 'marketplace'], 'type': 'string', 'description': 'What the flow does, so step counts are only compared with flows of the same kind. Inferred from screenType when omitted.'}, 'sections': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Page sections top to bottom, e.g. ["Hero", "Plan cards", "FAQ"].'}, 'flowSteps': {'type': 'array', 'items': {'type': 'string'}, 'description': 'For a multi-screen flow, each step\'s title in order, e.g. ["Sign up", "Verify email", "Create workspace"].'}, 'planCount': {'type': 'number', 'description': 'For pricing screens, how many plans are shown.'}, 'screenType': {'enum': ['landing', 'pricing', 'feature-page', 'sign-up', 'sign-in', 'verification', 'onboarding-step', 'plan-picker', 'empty-state', 'dashboard', 'list', 'detail', 'create-form', 'search', 'picker', 'booking', 'checkout', 'marketplace', 'settings', 'docs', 'menu', 'lesson'], 'type': 'string', 'description': 'What kind of screen it is.'}, 'description': {'type': 'string', 'description': 'One or two sentences on what the screen is for and how it is laid out, e.g. "Pricing page with three plan cards, a monthly/yearly toggle and a feature table".'}, 'primaryAction': {'type': 'string', 'description': 'The main button or action, e.g. "Start free trial".'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'next': {'type': 'string'}, 'report': {'type': 'string', 'description': 'Markdown summary of the comparison.'}, 'references': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'why': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'facts': {'type': 'array', 'items': {'type': 'string'}}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string'}, 'screenType': {'type': 'string'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}}}
compare_screens
Compare two 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 approach the same problem
differently—e.g. comparing Linear's pricing page with Stripe's pricing page, or Vercel's
onboarding with Notion's onboarding.
You can also compare one screen against a target description to see how close a reference
matches what the user is trying to build.
Read only
Input schema
{'type': 'object', 'required': ['screenA'], 'properties': {'focus': {'enum': ['layout', 'sections', 'actions', 'dimensions', 'typography', 'all'], 'type': 'string', 'default': 'all', 'description': 'What aspects to emphasize in the comparison.'}, 'screenA': {'type': 'string', 'description': 'First screen id to compare, e.g. linear-marketing-pricing.'}, 'screenB': {'type': 'string', 'description': 'Second screen id to compare. If omitted, provide targetDescription instead.'}, 'targetDescription': {'type': 'string', 'description': 'Instead of screenB, describe what you\'re building to see how screenA matches, e.g. "Pricing page with 3 tiers and a feature comparison table".'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'report': {'type': 'string', 'description': 'Markdown summary of the comparison between the two screens.'}, 'screenA': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'title': {'type': 'string'}, 'width': {'type': 'integer'}, 'height': {'type': 'integer'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string'}, 'screenType': {'type': 'string'}, 'actionCount': {'type': 'integer'}, 'productName': {'type': 'string'}, 'sectionCount': {'type': 'integer'}}, 'description': 'Details about the first screen.'}, 'screenB': {'type': 'object', 'nullable': True, 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'title': {'type': 'string'}, 'width': {'type': 'integer'}, 'height': {'type': 'integer'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string'}, 'screenType': {'type': 'string'}, 'actionCount': {'type': 'integer'}, 'productName': {'type': 'string'}, 'sectionCount': {'type': 'integer'}}, 'description': 'Details about the second screen (null if comparing against targetDescription).'}, 'differences': {'type': 'array', 'items': {'type': 'string'}, 'description': 'How the two screens differ.'}, 'observations': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Design observations and takeaways from the comparison.'}, 'similarities': {'type': 'array', 'items': {'type': 'string'}, 'description': 'What the two screens have in common.'}, 'targetDescription': {'type': 'string', 'description': 'The target description if comparing against text instead of screenB.'}}}
get_design
Get a product's design guide
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 language,
or borrow their typography and color choices for your own project.
Read only
Input schema
{'type': 'object', 'required': ['productId'], 'properties': {'context': {'enum': ['marketing', 'product'], 'type': 'string', 'description': 'Which surface to return. Omit for both.'}, 'productId': {'type': 'string', 'description': 'Product id from listProducts, e.g. linear, stripe or airbnb.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'font': {'type': 'string'}, 'product': {'type': 'string'}, 'summary': {'type': 'string'}, 'contexts': {'type': 'object', 'additionalProperties': {'type': 'object', 'properties': {'type': {'type': 'array', 'items': {'type': 'object'}}, 'theme': {'type': 'string'}, 'layout': {'type': 'array', 'items': {'type': 'string'}}, 'palette': {'type': 'array', 'items': {'type': 'object'}}, 'components': {'type': 'array', 'items': {'type': 'string'}}}}}}}
get_flow
Get a product's onboarding 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 structures their signup and onboarding, what information
they collect at each step, and how they guide users to activation.
Read only
Input schema
{'type': 'object', 'required': ['productId'], 'properties': {'productId': {'type': 'string', 'description': 'Product id from listProducts, e.g. linear, stripe or airbnb.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'steps': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'branch': {'type': 'boolean', 'description': 'True if this step is an alternate path'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string'}, 'transitions': {'type': 'array', 'items': {'type': 'object', 'properties': {'to': {'type': 'string', 'description': 'Where this action leads.'}, 'action': {'type': 'string', 'description': 'The button or link text.'}}}}}}}, 'captured': {'type': 'string', 'format': 'date'}, 'flowType': {'enum': ['signup-onboarding', 'search', 'checkout', 'booking', 'marketplace'], 'type': 'string'}, 'flowTitle': {'type': 'string'}, 'handoffId': {'type': 'string', 'description': 'Use with buildHandoff to get the full prompt.'}, 'productId': {'type': 'string'}, 'productName': {'type': 'string'}}}
get_product
Get one 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 notes and an image URL.
Read only
Input schema
{'type': 'object', 'required': ['productId'], 'properties': {'productId': {'type': 'string', 'description': 'Product id from listProducts, e.g. linear, stripe or airbnb.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'id': {'type': 'string'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'tags': {'type': 'array', 'items': {'type': 'string'}}, 'counts': {'type': 'object', 'properties': {'flow': {'type': 'integer'}, 'product': {'type': 'integer'}, 'marketing': {'type': 'integer'}}}, 'source': {'type': 'string'}, 'screens': {'type': 'object', 'properties': {'flow': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string', 'description': 'Screen-sized preview (the top of long pages). Present on pick options.'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}, 'product': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string', 'description': 'Screen-sized preview (the top of long pages). Present on pick options.'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}, 'marketing': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string', 'description': 'Screen-sized preview (the top of long pages). Present on pick options.'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}}}, 'captured': {'type': 'string', 'format': 'date'}, 'coverage': {'type': 'string'}, 'handoffs': {'type': 'array', 'items': {'type': 'string'}}, 'flowTitle': {'type': 'string'}, 'captureNote': {'type': 'string'}, 'description': {'type': 'string'}}}
get_screen
Get one 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.
Read only
Input schema
{'type': 'object', 'required': ['screenId'], 'properties': {'screenId': {'type': 'string', 'description': 'Screen id from searchScreens or getProduct, e.g. linear-signup.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'width': {'type': 'integer'}, 'branch': {'type': 'boolean'}, 'height': {'type': 'integer'}, 'source': {'type': 'string'}, 'actions': {'type': 'array', 'items': {'type': 'object', 'properties': {'to': {'type': 'string'}, 'label': {'type': 'string'}, 'region': {'type': 'object', 'properties': {'x': {'type': 'number'}, 'y': {'type': 'number'}, 'width': {'type': 'number'}, 'height': {'type': 'number'}}, 'description': 'Hotspot position as percentages of the image.'}}}}, 'product': {'type': 'string'}, 'captured': {'type': 'string', 'format': 'date'}, 'imageUrl': {'type': 'string'}, 'sections': {'type': 'array', 'items': {'type': 'object', 'properties': {'y': {'type': 'integer'}, 'title': {'type': 'string'}}}}, 'previewUrl': {'type': 'string'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}
get_screen_image
Get a screen's screenshot
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 below the fold.
Read only
Input schema
{'type': 'object', 'required': ['screenId'], 'properties': {'size': {'enum': ['preview', 'full'], 'type': 'string', 'default': 'preview', 'description': 'preview (default) keeps images small enough to view; full returns the original capture.'}, 'screenId': {'type': 'string', 'description': 'Screen id from searchScreens or getProduct, e.g. linear-signup.'}}, 'additionalProperties': False}
list_flows
List captured onboarding 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 how products guide users through multi-step processes like signup, onboarding, or checkout.
Read only
Input schema
{'type': 'object', 'required': [], 'properties': {'flowType': {'enum': ['signup-onboarding', 'search', 'checkout', 'booking', 'marketplace'], 'type': 'string', 'description': 'Only return flows of this type.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'flows': {'type': 'array', 'items': {'type': 'object', 'properties': {'flowType': {'enum': ['signup-onboarding', 'search', 'checkout', 'booking', 'marketplace'], 'type': 'string', 'description': 'What the flow accomplishes.'}, 'flowTitle': {'type': 'string', 'description': 'Human-readable title for the flow'}, 'handoffId': {'type': 'string', 'description': 'Use with buildHandoff'}, 'productId': {'type': 'string'}, 'stepCount': {'type': 'integer', 'description': 'Total steps including branches.'}, 'branchCount': {'type': 'integer', 'description': 'Steps that are alternate branches (not the main path).'}, 'productName': {'type': 'string'}}}}, 'total': {'type': 'integer'}}}
list_products
List captured 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,
Framer, and Supabase. Each has captured onboarding flows, marketing pages, and/or in-app screens.
Read only
Input schema
{'type': 'object', 'required': [], 'properties': {}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'products': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'tags': {'type': 'array', 'items': {'type': 'string'}}, 'counts': {'type': 'object', 'properties': {'flow': {'type': 'integer'}, 'product': {'type': 'integer'}, 'marketing': {'type': 'integer'}}}, 'source': {'type': 'string'}, 'captured': {'type': 'string', 'format': 'date'}, 'description': {'type': 'string'}}}}}}
pick_reference
Let the user pick a 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 they can evaluate long pages.
After calling this, tell them to choose in the picker, then call waitForPick with the pickId
to get their choice and a complete build prompt.
Input schema
{'type': 'object', 'required': [], 'properties': {'q': {'type': 'string', 'description': 'Search words, e.g. "pricing page", "onboarding", "empty state". The best matches become the options.'}, 'goal': {'type': 'string', 'description': 'What the user is building, shown on the page and used in the build prompt, e.g. "NSDR premium upgrade page".'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'Only search this kind of screen.'}, 'count': {'type': 'number', 'default': 3, 'description': 'How many options to show when searching, 2 to 6.'}, 'stack': {'type': 'string', 'description': 'Preferred stack for the build prompt.'}, 'product': {'type': 'string', 'description': 'Only search this product id.'}, 'screens': {'type': 'string', 'description': 'Comma-separated screen ids to show instead of searching, e.g. from an earlier searchScreens.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'url': {'type': 'string', 'description': 'Open this for the user.'}, 'next': {'type': 'string', 'description': 'What to do next.'}, 'pickId': {'type': 'string'}, 'status': {'enum': ['pending'], 'type': 'string'}, 'options': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string', 'description': 'Screen-sized preview (the top of long pages). Present on pick options.'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}, 'canvasUrl': {'type': 'string', 'description': 'Experimental pan-and-zoom canvas view of the same pick.'}}}
search_screens
Search screens
Search the UI reference catalog by keyword across titles, notes, page sections, and observed
actions. Filter by product or kind (flow/marketing/product).
Use this to find design pattern examples like "pricing page", "empty state", "date picker",
"onboarding step", "checkout form", "dashboard", "sign-up", "settings", etc. Returns the
best matches with screen IDs you can pass to getScreen or getScreenImage.
Read only
Input schema
{'type': 'object', 'required': [], 'properties': {'q': {'type': 'string', 'description': 'Keywords to match, e.g. "pricing page", "empty state", "onboarding". Omit to list everything that matches the filters.'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'Only return this kind of screen.'}, 'limit': {'type': 'number', 'default': 20, 'description': 'Maximum results, 1 to 50.'}, 'product': {'type': 'string', 'description': 'Only return screens from this product id, e.g. linear, stripe, airbnb.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'total': {'type': 'integer'}, 'screens': {'type': 'array', 'items': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'product': {'type': 'string'}, 'imageUrl': {'type': 'string'}, 'previewUrl': {'type': 'string', 'description': 'Screen-sized preview (the top of long pages). Present on pick options.'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}}}}
wait_for_pick
Wait for the user's 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 clicked "None of these fit", status is "dismissed"
and you should ask what they want instead.
Read only
Input schema
{'type': 'object', 'required': ['pickId'], 'properties': {'wait': {'type': 'number', 'default': 45, 'description': 'Seconds to wait for a choice, 0 to 50.'}, 'pickId': {'type': 'string', 'description': 'The pickId returned by pickReference.'}}, 'additionalProperties': False}
Output schema
{'type': 'object', 'properties': {'choice': {'type': 'object', 'properties': {'id': {'type': 'string'}, 'kind': {'enum': ['flow', 'marketing', 'product'], 'type': 'string', 'description': 'flow is an onboarding step, marketing a public web page, product an in-app screen.'}, 'notes': {'type': 'string'}, 'title': {'type': 'string'}, 'width': {'type': 'integer'}, 'branch': {'type': 'boolean'}, 'height': {'type': 'integer'}, 'source': {'type': 'string'}, 'actions': {'type': 'array', 'items': {'type': 'object', 'properties': {'to': {'type': 'string'}, 'label': {'type': 'string'}, 'region': {'type': 'object', 'properties': {'x': {'type': 'number'}, 'y': {'type': 'number'}, 'width': {'type': 'number'}, 'height': {'type': 'number'}}, 'description': 'Hotspot position as percentages of the image.'}}}}, 'product': {'type': 'string'}, 'captured': {'type': 'string', 'format': 'date'}, 'imageUrl': {'type': 'string'}, 'sections': {'type': 'array', 'items': {'type': 'object', 'properties': {'y': {'type': 'integer'}, 'title': {'type': 'string'}}}}, 'previewUrl': {'type': 'string'}, 'productName': {'type': 'string', 'description': 'Present on pick options.'}}}, 'pickId': {'type': 'string'}, 'prompt': {'type': 'string', 'description': 'Build prompt for the chosen reference.'}, 'status': {'enum': ['pending', 'chosen', 'dismissed'], 'type': 'string'}, 'message': {'type': 'string'}}}
History
Recent tool changes
Changed
wait_for_pick
Oct. 2, 2026, 2:40 a.m.
Changed
search_screens
Oct. 2, 2026, 2:40 a.m.
Changed
pick_reference
Oct. 2, 2026, 2:40 a.m.
Changed
list_products
Oct. 2, 2026, 2:40 a.m.
Added
list_flows
Oct. 2, 2026, 2:40 a.m.
Changed
get_screen_image
Oct. 2, 2026, 2:40 a.m.
Changed
get_screen
Oct. 2, 2026, 2:40 a.m.
Changed
get_product
Oct. 2, 2026, 2:40 a.m.
Added
get_flow
Oct. 2, 2026, 2:40 a.m.
Changed
get_design
Oct. 2, 2026, 2:40 a.m.
Added
compare_screens
Oct. 2, 2026, 2:40 a.m.
Changed
check_my_ui
Oct. 2, 2026, 2:40 a.m.
Changed
build_handoff
Oct. 2, 2026, 2:40 a.m.
Added
wait_for_pick
Sept. 30, 2026, 2:40 a.m.
Added
search_screens
Sept. 30, 2026, 2:40 a.m.
Added
pick_reference
Sept. 30, 2026, 2:40 a.m.
Added
list_products
Sept. 30, 2026, 2:40 a.m.
Added
get_screen_image
Sept. 30, 2026, 2:40 a.m.
Added
get_screen
Sept. 30, 2026, 2:40 a.m.
Added
get_product
Sept. 30, 2026, 2:40 a.m.
Added
get_design
Sept. 30, 2026, 2:40 a.m.
Added
check_my_ui
Sept. 30, 2026, 2:40 a.m.
Added
build_handoff
Sept. 30, 2026, 2:40 a.m.
Discover
Similar MCP servers
GripForge
io.github.gripforgeai/mcp
Generates, rigs, animates, analyzes, and packages game characters, weapons, armor, effects, environments, and engine-ready assets.
spriteship
com.spriteship/spriteship
Generates and manages 2D game characters, assets, animations, tilesets, UI packs, maps, and engine-ready exports for multiple gam…
Blixtworks
com.blixtworks.www/tools
Offers pay-per-call utilities for text, image processing and analysis, data conversion, validation, web inspection, cryptography,…
Compose Preview Catalogs
io.github.yschimke/compose-preview
Browses, renders, compares, audits, and edits Jetpack Compose preview catalogs and associated UI designs.
arch-tools-mcp
io.github.Deesmo/arch-tools-mcp
Provides general-purpose agent APIs for browser automation, web and PDF extraction, data conversion, email operations, fact check…
kernelcad
com.kernelcad/kernelcad
Authors, evaluates, reviews, simulates, edits, and exports parametric CAD assemblies and geometry from editable TypeScript-based …
floot
com.floot/floot
Creates, edits, previews, databases, and publishes full-stack web and mobile applications with hosted resources and deployment wo…
Raven
ai.ravenmcp/raven-mcp
Supports coding agents with design audits, design-system guidance, and a configurable visual preference profile.