{"id":"dev.motionprompts/motionprompts","slug":"dev-motionprompts-motionprompts","title":"motionprompts","description":"Plan pages, pick GSAP motion components and get their build prompts and composition rules.","version":"1.1.1","publisher":{"kind":"domain","id":"motionprompts.dev","label":"motionprompts.dev","url":"https://motionprompts.dev"},"website":"https://motionprompts.dev/developers/","repository":"https://github.com/VanguardiaAI/motionprompts-mcp","remotes":[{"type":"streamable-http","url":"https://motionprompts.dev/mcp","headers":[{"description":"Optional. 'Bearer mpk_...' from motionprompts.dev/account unlocks the full prompts of the paid catalog.","isSecret":true,"name":"Authorization"}]}],"packages":[{"registryType":"npm","registryBaseUrl":"https://registry.npmjs.org","identifier":"motionprompts-mcp","version":"1.1.1","transport":{"type":"stdio"}}],"published":"2026-10-20","updated":"2026-10-20","status":"online","auth":"","latency_ms":1196,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"search_components","title":"Search components","description":"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.","read_only":false},{"name":"get_component","title":"Get component","description":"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.","read_only":false},{"name":"list_facets","title":"List facets","description":"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.","read_only":false},{"name":"list_components","title":"List components","description":"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.","read_only":false},{"name":"list_motion_systems","title":"List motion systems","description":"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.","read_only":false},{"name":"get_motion_system","title":"Get one motion system with its members","description":"Full token set of a motion system plus the components that are native to it.","read_only":false},{"name":"search_components_motion","title":"Search components by measured motion metadata","description":"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.","read_only":false},{"name":"get_integration_contract","title":"Integration contract for a set of components","description":"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.","read_only":false},{"name":"plan_imagery","title":"Dirección de imagen de una página, sección a sección","description":"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","read_only":false},{"name":"plan_page","title":"Plan a page's information architecture from a brief","description":"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,","read_only":false},{"name":"suggest_mechanics","title":"Mechanics for ONE section, by its role","description":"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","read_only":false},{"name":"suggest_page_treatments","title":"Mechanics that apply to the PAGE, not to a section","description":"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","read_only":false},{"name":"get_component_prompt","title":"Get a component prompt + motion tokens (no rendering)","description":"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","read_only":false},{"name":"render_prompt","title":"[DEPRECATED — use get_component_prompt] Render a prompt by mechanical substitution","description":"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', '","read_only":false}],"server_info":{"name":"motionprompts","version":"1.0.0"},"category":"design","tags":["agents","image-video","web-search"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-20","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/dev-motionprompts-motionprompts/"}