Blender integration through the Model Context Protocol
Nothing to run from here
Screenrove is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Real product UI captures (onboarding, pricing, in-app screens) with design guides for coding agents.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http screenrove-mcp https://screenrove.com/mcp
# 2 — ask your agent for something these tools do
# build_handoff, check_my_ui, get_design and 7 more
Screenrove costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SCAll 1 server
screenrove1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http screenrove-mcp https://screenrove.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Build the same ready-to-follow prompt as the "Use in agent" button: ordered screens with notes, observed transitions, image URLs, the design guide and an implementation checklist. Use a product's onboarding flow ({product}-onboarding), its whole collection ({product}-collection) or any single screen id.
No parameter schema on file.
Find the real product screens closest to the user's own screen or flow and compare them: step counts, plan counts, page sections. First look at the user's screenshot or running app yourself, then describe its structure in these fields. Do not send the image, and leave out real names, emails, prices or customer data: structure only. Returns a short report with the closest references (the best match
No parameter schema on file.
Get the measured design guide for a product: font, palette, type scale, layout and component notes. Marketing site and product UI are measured separately.
No parameter schema on file.
Get a product's coverage notes, design summary and every screen it contains, grouped into the onboarding flow, marketing pages and in-product screens.
No parameter schema on file.
Get everything recorded about one screen: notes, source URL, image URLs and dimensions, observed actions and where they lead, and page sections for long pages.
No parameter schema on file.
Get the screenshot itself so you can look at it. 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.
No parameter schema on file.
List every product in the library with its capture date, tags, coverage notes and screen counts. Start here to see what references exist.
No parameter schema on file.
Show the user a few matching references side by side in their browser and let them click the one to build from. Prefer this over sending full-page images whenever the user should decide. Returns a url: open it for them (run open <url> on macOS, xdg-open <url> on Linux, or show the link), tell them to choose, then call waitForPick with the pickId.
No parameter schema on file.
Search every captured screen by keyword across titles, notes, page sections and observed actions. Filter by product or kind. Use this to find references like "pricing page", "empty state" or "date picker".
No parameter schema on file.
Wait for the user to choose on the pick page. 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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Screenrove or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Screenrove can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.