# motionprompts (npm · motionprompts-mcp)

Plan pages, pick GSAP motion components and get their build prompts and composition rules.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `motionprompts.dev`: 69/100, [markdown](https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts.md), [page](https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts)
- npm · `motionprompts-mcp`: 68/100 (this document), [markdown](https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp.md), [page](https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp)

## Channel facts

- Registry: `npm`
- Package: `motionprompts-mcp`
- Version: `1.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - 96% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 13396 tokens (~48/item across 274 items; 14 tools + 260 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 76% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the motionprompts MCP server?

motionprompts runs locally as an npm package, launched with npx -y motionprompts-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dev-motionprompts-motionprompts -- npx -y motionprompts-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "dev-motionprompts-motionprompts": {
      "command": "npx",
      "args": [
        "-y",
        "motionprompts-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-motionprompts-motionprompts": {
      "command": "npx",
      "args": [
        "-y",
        "motionprompts-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-motionprompts-motionprompts -- npx -y motionprompts-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-motionprompts-motionprompts": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "motionprompts-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-motionprompts-motionprompts --command npx --arg -y --arg motionprompts-mcp
```

### Hermes

```yaml
mcp_servers:
  dev-motionprompts-motionprompts:
    command: "npx"
    args: ["-y", "motionprompts-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-motionprompts-motionprompts": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "motionprompts-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-motionprompts-motionprompts -t stdio -c npx -a -y motionprompts-mcp
```

### Other

```json
{
  "mcpServers": {
    "dev-motionprompts-motionprompts": {
      "command": "npx",
      "args": [
        "-y",
        "motionprompts-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-21 (score 68, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-20 (score 53)

First indexed and scored.

## MCP tools (14)

### `search_components` (~361 tokens)

Search components

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.

Input parameters:

- `category` (array): Animation-family filter (e.g. scroll, cards, menu, 3d-webgl).
- `deps` (array): Require these runtime deps (e.g. ["three"], ["lenis"]). AND semantics.
- `level` (array): page (owns the whole page/scroll) | section (a block) | widget (small embeddable).
- `limit` (integer): Max results (default 12).
- `maxPerfCost` (string): Cap runtime weight: light | medium | heavy.
- `mobileSafe` (boolean): If true, only components that degrade well on touch/small screens.
- `mood` (array): Aesthetic filter. One of: minimal, elegant, luxury, editorial, bold, playful, corporate, retro, futuristic, experimental, cinematic, brutalist, organic, technical
- `query` (string): Free-text brief or component name/alias. Spanish or English; accent-insensitive.
- `useCase` (array): 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…

### `get_component` (~135 tokens)

Get component

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.

Input parameters:

- `include` (array): Which payloads to return. Default: ["meta","preview","prompt"].
- `slug` (string, required): Component slug, e.g. "brandappart-sticky-cards".

### `list_facets` (~49 tokens)

List facets

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.

### `list_components` (~80 tokens)

List components

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.

Input parameters:

- `limit` (integer): Max items (default: all).
- `offset` (integer): Skip N items (pagination).

### `list_motion_systems` (~66 tokens)

List motion systems

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.

### `get_motion_system` (~42 tokens)

Get one motion system with its members

Full token set of a motion system plus the components that are native to it.

Input parameters:

- `name` (string, required): System name, e.g. scrub-lagged.

### `search_components_motion` (~139 tokens)

Search components by measured motion metadata

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.

Input parameters:

- `category` (string)
- `complexity` (integer)
- `libs` (array): Todas deben estar presentes.
- `limit` (integer)
- `max_complexity` (integer)
- `motion_system` (string)
- `trigger` (string)

### `get_integration_contract` (~151 tokens)

Integration contract for a set of components

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.

Input parameters:

- `motion_system` (string)
- `moving_sections`: 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.
- `slugs` (array, required)

### `plan_imagery` (~301 tokens)

Dirección de imagen de una página, sección a sección

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), la receta de transparencia (alfa real de gpt-image-2.5 con `background: transparent`, ya sin magenta), la del retoque con referencia (image-to-image para corregir un detalle sin volver a tirar el dado), la de las hojas de seis recortes por generación, y de dónde salen los logotipos reales (Wikimedia, nunca generados). NO genera imágenes, no usa ninguna clave y no hace ninguna llamada de red: devuelve texto. Llámala DESPUÉS de plan_page y ANTES de escribir un solo prompt de imagen.

Input parameters:

- `archetype` (string)
- `brief` (string): El mismo brief que le diste a plan_page.
- `palette` (array): La paleta ya fijada: las tomas obedecen al diseño, no al revés.
- `sections` (array): Las secciones de plan_page, tal cual. Sin esto sólo se devuelven las reglas generales.

### `plan_page` (~233 tokens)

Plan a page's information architecture from a brief

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, one section at a time, with suggest_mechanics. It also names the roles the catalog cannot cover, so you write those from the system tokens instead of adopting the least-bad search hit. An optional `reference` contributes STATIC art direction and biases the motion system — motion is NEVER derived from the reference.

Input parameters:

- `archetype` (string): Fuerza el patrón de arquitectura en vez de detectarlo del brief. Uno de: agency, restaurant, product-brand, saas, portfolio, event, editorial
- `brief` (string, required): e.g. 'tostaduría de café de especialidad', 'agencia de software a medida'.
- `reference` (object)

### `suggest_mechanics` (~436 tokens)

Mechanics for ONE section, by its role

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 accordions, data tables) instead of returning the least-bad hit dressed up as an answer — search_components cannot tell you that, and its top result for 'accordion' is a horizontal image gallery. When the verdict is `none`, write the section from the motion system tokens; that is a legitimate outcome, not a failure.

Input parameters:

- `adopted` (array): 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…
- `avoid` (array): 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.…
- `limit` (integer): Max candidates (default 5).
- `motion_system` (string): The page's system; ranks compatible components first and is echoed back when there is nothing to adopt.
- `need` (string): What this section must do, in prose. e.g. 'the roast curve draws itself as you scroll'.
- `role` (string, required): 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

### `suggest_page_treatments` (~280 tokens)

Mechanics that apply to the PAGE, not to a section

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 butt every section together with a straight line. A treatment does NOT consume a section and does NOT count toward motion_coverage; it adds on top. Some kinds are decisions rather than components (`scroll-suave`) and come back with verdict `not-a-component` instead of a fake candidate list. Still pass whatever you adopt to get_integration_contract: treatments compete for the same capabilities (scroll owner, document height) as any other component.

Input parameters:

- `avoid` (array): Slugs to exclude.
- `kind` (string, required): Treatment kind. One of: scroll-suave, frontera-de-seccion, fondo-continuo, cursor, transicion-de-ruta
- `limit` (integer): Max candidates (default 5).
- `motion_system` (string): The page's system; echoed back when there is nothing to adopt.
- `need` (string): What it has to do, in prose. Only reorders within the kind's pool.

### `get_component_prompt` (~155 tokens)

Get a component prompt + motion tokens (no rendering)

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, which substituted mechanically and produced prompts whose prose contradicted their code (11/30 in judged evaluation). See DECISIONS.md D15 and D18.

Input parameters:

- `motion_system` (string): Default: the component's native system.
- `slug` (string, required)

### `render_prompt` (~240 tokens)

[DEPRECATED — use get_component_prompt] Render a prompt by mechanical substitution

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', 'durations are 1'), and substituting those would make prose and code contradict each other. For those components this returns the prompt unchanged. See DECISIONS.md D15. Returns the component's build prompt with its motion tokens (ease/duration/stagger) replaced by the chosen motion system's values, so several components share one timing language. Values that are STRUCTURAL to the effect (elastic overshoot, loop cadence, scrub linearity, shader/physics constants) are never substituted — they come back listed under 'Valores no parametrizables'. Omit `system` to use the component's native one.

Input parameters:

- `slug` (string, required): Component slug.
- `system` (string): Motion system name. Default: the component's native system.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp#diagnostics

## Score history

- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 53

## Common questions

### What is the motionprompts MCP server?

motionprompts is an MCP server listed in the public MCP registry as dev.motionprompts/motionprompts. Plan pages, pick GSAP motion components and get their build prompts and composition rules. This page covers its npm package (motionprompts-mcp).

### Is the motionprompts MCP server safe to use?

motionprompts scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the motionprompts MCP server expose?

motionprompts exposes 14 tools: search_components, get_component, list_facets, list_components, list_motion_systems, and 9 more. Their descriptions and schemas cost roughly 2,668 tokens of context every time the server is loaded.

### Is the motionprompts MCP server still maintained?

motionprompts is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/motionprompts-mcp
- Socket report: https://socket.dev/npm/package/motionprompts-mcp
- Repository: https://github.com/VanguardiaAI/motionprompts-mcp
- Website: https://motionprompts.dev/developers/
- Changelog RSS feed: https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dev-motionprompts-motionprompts/motionprompts-mcp