Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Nothing to run from here
motionprompts 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.
98/100
trust score
12
downloads a day
local
or remote
149
downloads in 30d
What it does
Plan pages, pick GSAP motion components and get their build prompts and composition rules.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user motionprompts-mcp '--' npx -y motionprompts-mcp
# 2 — ask your agent for something these tools do
# search_components, get_component, list_facets and 11 more
motionprompts costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 1 server
motionprompts1 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. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user motionprompts-mcp '--' npx -y motionprompts-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Or connect to its publisher’s address
Its publisher also runs it at https://motionprompts.dev/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http motionprompts-mcp https://motionprompts.dev/mcpFree on mcprush, and it runs from its publisher’s own package: 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 your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
14 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Find the components that best fit a natural-language brief (e.g. "un hero elegante para una marca de lujo", "cartas apiladas al hacer scroll") or a name/alias. Returns a ranked, compact list with a why for each hit. Combine the free-text query with facet filters to narrow. Then call get_component on the chosen slug. Leave query empty to browse purely by filters.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text brief or component name/alias. Spanish or English; accent-insensitive. |
| mood | array | no | Aesthetic filter. One of: minimal, elegant, luxury, editorial, bold, playful, corporate, retro, futuristic, experimental, cinematic, brutalist, organic, technical |
| useCase | array | no | Page-role filter. One of: hero, preloader, page-transition, navigation, footer, gallery, slider, card-deck, scroll-story, image-reveal, text-reveal, hover-interaction, cursor-effect, logo, background, |
| level | array | no | page (owns the whole page/scroll) | section (a block) | widget (small embeddable). |
| category | array | no | Animation-family filter (e.g. scroll, cards, menu, 3d-webgl). |
| deps | array | no | Require these runtime deps (e.g. ["three"], ["lenis"]). AND semantics. |
| maxPerfCost | string | no | Cap runtime weight: light | medium | heavy. |
| mobileSafe | boolean | no | If true, only components that degrade well on touch/small screens. |
| limit | integer | no | Max results (default 12). |
Fetch one component by slug. include controls the payload: 'meta' (full catalog record), 'preview' (thumbnail + live demo URL), 'prompt' (a self-contained brief to REBUILD it faithfully), 'source' (the actual index.html/styles.css/script.js to copy, plus an integration note). Default: meta + preview + prompt. Add 'source' when you want the real code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Component slug, e.g. "brandappart-sticky-cards". |
| include | array | no | Which payloads to return. Default: ["meta","preview","prompt"]. |
Return the filter vocabulary (mood, useCase, level, perfCost, category, deps) with how many components carry each value. Call this first to learn the exact values search_components accepts.
No parameter schema on file.
Browse the whole catalog as a compact list (slug, title, useWhen, mood, useCase, level, perfCost). Use for an overview or when a brief is vague; use search_components when you have a specific brief.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items (default: all). |
| offset | integer | no | Skip N items (pagination). |
The 8 motion systems of the library: token sets (ease/duration/stagger/lenis) derived from the measured inventory, not invented. Use this FIRST when composing a page: pick one system and render every component's prompt with it so the page moves coherently.
No parameter schema on file.
Full token set of a motion system plus the components that are native to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | System name, e.g. scrub-lagged. |
Filters by the CAPA-1 motion block (trigger, libs, complexity, motion system) rather than by prose. Prefer this over search_components when composing a page: category describes how a component LOOKS, trigger/cluster describe how it MOVES, and they disagree — the slider label alone splits across 3 opposite physics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | — |
| trigger | string | no | — |
| libs | array | no | Todas deben estar presentes. |
| complexity | integer | no | — |
| max_complexity | integer | no | — |
| motion_system | string | no | — |
| limit | integer | no | — |
Given the slugs you intend to put on ONE page, returns: rule violations (hard, invalidate the page), warnings, the measured budget (JS gzip / assets / scroll corridor), and an ordered init plan — single Lenis instance, CustomEase registration, entry veil first, one ScrollTrigger.refresh() at the end, WebGL loop gating. Every step cites the evidence it comes from.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | — |
| motion_system | string | no | — |
| moving_sections | no | Las secciones que DEBEN moverse (plan_page → motion_coverage.must_move), o cuántas son. Con esto el contrato audita la cobertura y te dice si te has quedado corto. |
Qué imagen necesita cada sección, CON QUÉ MODELO se hace y cómo se redacta el prompt. Con la arquitectura y el movimiento resueltos, lo que sigue delatando una página generada son las imágenes: genéricas del sector en vez de específicas de la sección, sin una sola persona, y todas rectángulos con fondo. Esta tool devuelve el enrutado por modelo (personas ≠ objetos ≠ paisaje: no son intercambiables
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | no | El mismo brief que le diste a plan_page. |
| archetype | string | no | — |
| sections | array | no | Las secciones de plan_page, tal cual. Sin esto sólo se devuelven las reglas generales. |
| palette | array | no | La paleta ya fijada: las tomas obedecen al diseño, no al revés. |
Returns the SECTIONS a page of this kind needs — 10 to 14 of them, each with a role, what it has to accomplish, what content it needs, and whether it should move — plus a motion system and its tokens. It returns NO components on purpose: a page can only be as rich as the list it is composed from, and composing from animation mechanics caps every page at five sections. Ask for mechanics afterwards,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | e.g. 'tostaduría de café de especialidad', 'agencia de software a medida'. |
| archetype | string | no | Fuerza el patrón de arquitectura en vez de detectarlo del brief. Uno de: agency, restaurant, product-brand, saas, portfolio, event, editorial |
| reference | object | no | — |
Given a section role from plan_page and what that section has to do, returns ranked candidate components — filtered first by the catalog facets that actually correspond to the role, then ranked by the free-text need. Prefer this over search_components when building a planned page. Crucially, it can answer that the catalog has NOTHING for a role (counters, progress bars, pricing tables, FAQ accordi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | yes | Section role from plan_page. One of: entry, chrome, hero, proof, thesis, feature, collection, process, signature, context, explainer, people, cta, footer, data, pricing, testimonial, faq, reference |
| need | string | no | What this section must do, in prose. e.g. 'the roast curve draws itself as you scroll'. |
| motion_system | string | no | The page's system; ranks compatible components first and is echoed back when there is nothing to adopt. |
| limit | integer | no | Max candidates (default 5). |
| avoid | array | no | Slugs to exclude — pass everything you already used on OTHER pages. Wide roles offer 100+ candidates whose top scores are statistically tied, so without this you will keep adopting the same handful. N |
| adopted | array | no | What you have ALREADY adopted on THIS page. Candidates that would invalidate the page alongside them come back with composes_with_adopted: false, the reason in collision, and sorted last. Without |
The twin of suggest_mechanics for the family that does not fill a section slot: smooth scroll, the shaped edge BETWEEN two stacked sections, a background that runs behind the whole page, a custom cursor, route transitions. These were unreachable from the planner because the whole model assumed a mechanic occupies one slot in sections — which is why a page could be planned end to end and still bu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | Treatment kind. One of: scroll-suave, frontera-de-seccion, fondo-continuo, cursor, transicion-de-ruta |
| need | string | no | What it has to do, in prose. Only reorders within the kind's pool. |
| motion_system | string | no | The page's system; echoed back when there is nothing to adopt. |
| limit | integer | no | Max candidates (default 5). |
| avoid | array | no | Slugs to exclude. |
THE way to get a build prompt. Returns three blocks: (a) the standalone prompt VERBATIM, untouched; (b) the tokens of the requested motion system; (c) an explicit instruction telling you to adapt (a) to (b) YOURSELF, preserving arithmetic relationships — if a duration holds up a sum, a chained sequence or a ScrollTrigger end, recompute the whole set, never a lone value. Replaces render_prompt, w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| motion_system | string | no | Default: the component's native system. |
DEPRECATED in favour of get_component_prompt. Mechanical substitution does not fit this corpus: the prompts narrate their own numbers in prose, so replacing only the code values makes prose and code specify different components (judged 11/30). Coverage is deliberately narrow: 164 of 219 components have ZERO substitutable values because their prompts narrate their own numbers in prose ('over 4s', '
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Component slug. |
| system | string | no | Motion system name. Default: the component's native system. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public; its licence metadata reads NOASSERTION rather than naming a licence
- Runs on your machine — nothing of it reaches our gateway
- 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 motionprompts 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: —
ATrust score 98 / 100
Release 1.1.1 · scanned 20 Oct 2026
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.
Threat score100
Client score98
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationnone
Surface digest2a47af1f5d07892c5355ebeee6a12df20216192c611a54bf10de018405b90610
Score vectorthreat 100 → client 98
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_components | untrusted-input | untrusted-input: keyword "browse" |
| get_component | untrusted-input | untrusted-input: keyword "fetch" |
| list_facets | no tags | |
| list_components | untrusted-input | untrusted-input: keyword "browse" |
| list_motion_systems | no tags | |
| get_motion_system | no tags | |
| search_components_motion | no tags | |
| get_integration_contract | no tags | |
| plan_imagery | no tags | |
| plan_page | no tags | |
| suggest_mechanics | no tags | |
| suggest_page_treatments | no tags | |
| get_component_prompt | no tags | |
| render_prompt | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest2a47af1f5d07892c
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.1.1. Pin a release below and the command asks for exactly that one.
1.1.1
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 motionprompts 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.