Blender integration through the Model Context Protocol
Motion Menu 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.
What it does
597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http motion-menu-mcp https://www.motionmenu.ca/api/mcp
# 2 — ask your agent for something these tools do
# list_patterns, get_pattern, get_kit and 8 more
Motion Menu costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 motion-menu-mcp https://www.motionmenu.ca/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
11 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.
List Motion Menu patterns. Every row is "number slug <role> [tags] · title". ROLE is where the pattern goes on a page (hero, nav, pricing, background, product, form…) — filter by it when you are building a page rather than hunting an effect. The SLUG is the permanent identity — prefer it. Filter by tag (e.g. "scroll", "webgl", "seam", "commerce"), by collection slug (e.g. "seams-handoffs"), by
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | optional substring filter on title/description |
| role | string | no | WHERE IT GOES on a page — hero, nav, footer, pricing, background, gallery, product, form, stats, testimonial, cta, content, seam, chrome, type. Start here when building a page. |
| tag | string | no | optional tag, e.g. "scroll", "glsl", "commerce" |
| collection | string | no | optional collection slug, e.g. "webgl-3d" |
| section | string | no | legacy section letter, e.g. "J" — tags supersede this |
Get one pattern by number, including its complete transplantable HTML, CSS and JS. Pass framework to get a ready-to-use component wrapper (react .tsx, vue .vue, svelte .svelte, or vanilla .ts).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | permanent identity, e.g. "velocity-image-bend" — preferred |
| number | string | no | pattern number, e.g. "84" — a permanent alias for the slug |
| framework | string | no | component wrapper format (default: raw HTML/CSS/JS) |
Get the Motion Menu build kit: the design laws, the one-page act protocol, stack pins, known gotchas, and the full pattern index. Call this FIRST before building a page.
No parameter schema on file.
Get the machine-readable Motion Menu quality contract. Call before build_page. It defines anti-generic composition rules, motion lifecycle, responsive requirements, truth constraints, and release verification gates.
No parameter schema on file.
Check whether patterns you already built with have changed. Pass the library version you last built against (from version in a previous check_updates or /p/manifest.json) and get back exactly which slugs were added, changed or removed — so you re-pull three patterns instead of all of them. Call with no arguments to read the current version and library counts. Record the version you get back alon
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | no | The library version you built against. Omit to just read the current one. |
Intent-aware pattern recommendations. Describe what you are building — industry, style, mood, technical needs — and get scored results with reasons and compatibility suggestions. Returns metadata only (number, slug, title, role, score, reason, compatible_with). Call get_pattern to retrieve the actual code for any recommendation.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | What you are building, e.g. "premium SaaS landing page for enterprise AI startup" or "dark minimal portfolio with dramatic 3D hero" |
| role | string | no | Optional page-role filter (hero, nav, pricing, footer, background, etc.) |
| count | number | no | Max results (default 5, max 20) |
| context | array | no | Slugs or numbers already chosen for this page (order does not matter here). Recommendations that clash with any of them are excluded, a pattern already at its own max_per_page in context is skipped, a |
| seed | string/number | no | Reproducible creative seed. The same brief and seed return the same candidates; change it to explore another valid realization. |
| history | array | no | Recently used pattern slugs or numbers. They receive a strong cooldown penalty instead of dominating every session. |
| exclusions | array | no | Pattern slugs or numbers that must not be returned. |
Turn a business/page brief into three deliberately different design genomes before choosing components. Each direction defines layout grammar, typography, imagery, motion physics, density rhythm, and explicit avoid rules. Pass a returned direction_id into build_page with the same brief and seed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | Business, audience, offer, conversion goal, real assets, and brand constraints. |
| seed | string/number | no | Reproducible creative seed. |
Design a complete page from intent. Returns an act map — 5–7 acts in page order, each with a purpose, recommended patterns (by slug), and a density rating (loud/quiet). Follows the one-page protocol: density wave pacing, one GL spectacle, 12–18 viewport-heights. Feed the result straight to get_pattern to retrieve the code. Returns metadata only — no pattern bodies.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | yes | What the page is for, e.g. "luxury real estate landing page" or "SaaS startup launch with pricing" |
| acts | number | no | Number of acts (default 6, range 5–7) |
| direction_id | string | no | One direction_id returned by propose_directions for this same intent/seed. |
| seed | string/number | no | Reproducible creative seed. |
| history | array | no | Recently used pattern slugs or numbers to cool down. |
| exclusions | array | no | Pattern slugs or numbers that must not be used. |
Check whether a set of patterns work well together. Pass the slugs (or numbers) of patterns you plan to combine on a page and get a compatibility report: overall score, per-pair analysis, style/industry coherence, intensity balance, page-flow coverage, and warnings (duplicate roles, missing positions, too many heavy patterns). Call BEFORE building to catch mismatches early.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| components | array | yes | Pattern slugs or numbers to validate together |
Audit an EXISTING page (yours or a client's — any AI builder, any stack) for the default-AI "section grammar" tell: numbered steps, a centered hero with two buttons, 3-up icon cards, a testimonial/FAQ/CTA-band skeleton repeating unchanged. Deterministic, no LLM — every finding cites the exact matched HTML. Returns an ai_shaped_score (0-100), per-section tells with evidence, page-level tells (skele
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html | string | no | the page's full HTML — one page per call; a multi-page site is the caller's own loop |
| url | string | no | alternative to html — fetched server-side (https only, public addresses only, 3 MB cap, 10 s timeout, no redirect to a private range, no credentials forwarded) |
Re-audit a page you just rewrote from audit_page's prescriptions and get a pass/fail verdict: fresh ai_shaped_score, the delta from the prior audit (pass baseline_score or the whole prior audit_page result as baseline), and any tells STILL present, each with a concrete fix instruction. FREE, no key required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| html | string | yes | the rewritten page's full HTML |
| baseline_score | number | no | optional — the ai_shaped_score from the prior audit_page call, for a pass/fail delta |
| baseline | object | no | optional — the whole prior audit_page result, for a per-section tell-count delta in addition to the overall score delta; baseline_score is derived from it if omitted |
- 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 Motion Menu or to call it, at any volume.
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 16.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Motion Menu can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.