Screenrove: UI Design Reference & Screenshots (free Mobbin alternative)

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Entwicklertools

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://screenrove.com/mcp

claude mcp add --transport http screenrove https://screenrove.com/mcp

{
  "mcpServers": {
    "screenrove": {
      "url": "https://screenrove.com/mcp"
    }
  }
}

{
  "servers": {
    "screenrove": {
      "type": "http",
      "url": "https://screenrove.com/mcp"
    }
  }
}

https://screenrove.com/mcp

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 6. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

• 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 si

• 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 structur

• 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 counts, section order, blocks the references

• 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 limits, captured date and page url, plu

• 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).

• 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-theme copy folds into its row as variants.

• 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 " or "trustworthy like ": take the tokens from here and the structure from its scr

• 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 product structures signup, onboarding or a

• 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 the original source where its license a

• 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 and tags. Use it to explore a competitor's

• 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 not the screen: call get_screen_image w

• 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 is the original (often 2x), refused abo

• 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 steps; flows with no type are left out

• 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 or q; the first page also counts product

• 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=board-view or state=empty.

• 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 proposing names.

• 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 is there to choose: autonomous agents s

• 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 symbols". Logos are trademarks of their owner

• 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 spec and most with vanilla code. Any word

• 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 on .ai". Traits are heuristics; check t

• 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, facets combine with AND, e.g. pattern=list-v

• 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 only replacements. Then get_motion each on

• 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" means none fit: ask what they want. A pi

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026

• ! Vorsicht

  Entwickler passt zum Repo

  Die Registry nennt kein Quell-Repo, deshalb können wir den Herausgeber (screenrove.com) nicht dem Code zuordnen

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 3200 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 24 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Entwicklertoolsi

• Mehr Sterne als 0 % der anderen 4906 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 82 % der anderen 4906 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 24 % der anderen 4906 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

Keine README im Repo gefunden