Skip to main content
Refero MCP gives your agent tools for three research layers:
  1. Styles — visual direction, taste, tokens, typography, spacing, surfaces, imagery, and component feel.
  2. Screens — concrete UI patterns, page structure, copy, states, and product-specific details.
  3. Flows — multi-step journey logic: goals, actions, system responses, friction, and completion states.
For visual design work, start with styles. Use screens for concrete interface decisions. Use flows when the task has a before/after sequence.

Styles

refero_search_styles

Search curated design styles using semantic search. Use this first when you need visual direction, brand feel, typography, color, layout, spacing, elevation, surfaces, components, imagery, or design-system inspiration. Parameters Good queries
  • editorial monochrome SaaS landing page
  • premium fintech website with restrained typography
  • developer tool website with product screenshots
  • data infrastructure website dark technical style
  • Attio editorial SaaS typography
  • Linear changelog dark developer tool
Response shape
Search several visual angles before choosing a direction. Styles are reference ingredients, not templates to copy.

refero_get_style

Retrieve full design guidance for one or more style UUIDs. Use this after refero_search_styles. Parameters What you get
  • north star / visual thesis
  • color roles, not just hex values
  • typography roles and type scale
  • spacing, radius, shadows, elevation, and surfaces
  • layout and section rhythm
  • component treatments and sometimes implementation snippets
  • imagery, graphics, illustration, or product screenshot guidance
  • do/don’t rules and agent prompt guidance
Styles currently focus on web marketing and product pages: landing pages, pricing pages, product marketing sites, editorial brand sites, and SaaS websites. They are still useful for product UI work, but use screens and flows for product-specific behavior.

Screens

refero_search_screens

Search real UI screens for concrete interface decisions: page structure, component choices, content hierarchy, states, copy, and product patterns. Parameters Good queries
  • pricing page annual monthly toggle
  • feature comparison table
  • dashboard empty state
  • billing settings cancellation modal
  • 2FA setup recovery codes
  • data table filters
Response shape
Use page for pagination. Do not pass limit, offset, image_size, or include_similar to search tools.

refero_get_screen

Get full metadata and descriptions for one or more screens by UUID. Parameters Response shape

refero_get_similar_screens

Find visually and functionally similar screens for a screen UUID. Parameters Use this when one result is especially relevant and you want comparable examples quickly.

refero_get_screen_image

Return raw screenshot image content for a screen UUID. Parameters Use this only when text metadata is not enough and the agent needs to visually inspect the exact screenshot.

Flows

refero_search_flows

Search multi-step journeys: onboarding, checkout, signup, cancellation, upgrade, account deletion, password reset, and settings changes. Parameters Good queries
  • signup onboarding
  • checkout with promo code
  • subscription cancellation with retention offer
  • account deletion feedback
  • password reset 2FA
Response shape

refero_get_flow

Get the complete flow with all steps, goals, actions, system responses, screen metadata, and related search queries. Parameters Response shape

Common mistakes

  • Do not use old _tool suffixed names.
  • Do not call get_design_guidance; use styles, screens, and flows.
  • Do not pass image_size or include_similar to refero_get_screen.
  • Do not use numeric screen IDs. Screens use UUIDs.
  • Do not use screens as the main source for visual taste when styles are available.
  • Do not copy a single style directly.

Next

Data Model

Field reference for styles, screens, and flows.

Examples

Simple research workflows using current tools.

Refero Skill

Research-first design methodology for agents.