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

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

• 연결 방식: 클라우드에서 실행
• 전송 방식: Streamable HTTP
• 카테고리: 개발자 도구

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

검사 2/3 통과 · 내가 묻는 내용은 제작자 서버(screenrove.com)를 거쳐요

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"
    }
  }
}

어떤 앱에서 쓸 수 있나요

이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.

인터넷으로 연결하는 앱

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

모든 앱과 장단점 →

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

• 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

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 11일 점검

• ! 주의

  제작자와 저장소 일치

  레지스트리에 소스 저장소가 없어서, 게시자(screenrove.com)와 코드를 맞춰 볼 수 없어요

• … 아직 점검 안 함

  계속 관리되고 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• … 아직 점검 안 함

  라이선스 있음

  아직 GitHub에서 이 저장소를 읽어 오지 않았어요

• ✓ 통과

  엔드포인트 응답

  3200ms 만에 응답(HTTP 200)

• – 해당 없음

  OAuth로 로그인

  로그인 필요 없음

• ✓ 통과

  도구 설명에 숨겨진 지시 없음

  도구 설명 24개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

사용자 리뷰

아직 리뷰가 없어요

Google로 로그인하고 리뷰 쓰기

개발자 도구 카테고리의 다른 서버와 비교i

• 이 카테고리의 다른 서버 5759개 중 0%보다 스타가 많아요
• 이 카테고리의 다른 서버 5759개 중 68%보다 최근에 레지스트리에 공개됐어요
• 기본 점검 결과가 이 카테고리의 다른 서버 5759개 중 28%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

REA

Reverse engineer anything from your terminal or agent with one CLI and MCP server.

제작자: morluto·널리 사용됨·↓ 38.9만/주·★ 44.8만·17일 전 업데이트

내 컴퓨터에서 실행

설치

Netdata

Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.

제작자: netdata·널리 사용됨·★ 8.1만·7일 전 업데이트

클라우드에서 실행

설치

Front-End Checklist

Review frontend code and live pages against 386 quality-gated web development rules.

제작자: thedaviddias·널리 사용됨·★ 7.5만·37일 전 업데이트

클라우드에서 실행

설치

제작자의 README

저장소에서 README를 찾지 못했어요