Motion Menu Director
597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free.
使うべきか
品質と安全性
検出事項(5)
- HIGH
- MEDIUMcritique_page 内
- MEDIUMverify_complete 内
- INFOcritique_page 内
- INFOverify_complete 内
ツール定義とプロトコルへの準拠に関する自動分析に基づいています。
コンテキストコスト
これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。
インストール
ワンクリックインストール
これを `claude_desktop_config.json` ファイルに追加してください:
{
"mcpServers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}リモートエンドポイント
https://www.motionmenu.ca/api/mcpstreamable-httpできること
ツール一覧
ツール(15)
🟢list_patterns(query, role, tag, collection, section)
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 free-text query, or by legacy section letter. Call with no arguments to see the whole catalogue and its tag vocabulary.
入力スキーマ
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "optional substring filter on title/description"
},
"role": {
"type": "string",
"description": "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": {
"type": "string",
"description": "optional tag, e.g. \"scroll\", \"glsl\", \"commerce\""
},
"collection": {
"type": "string",
"description": "optional collection slug, e.g. \"webgl-3d\""
},
"section": {
"type": "string",
"description": "legacy section letter, e.g. \"J\" — tags supersede this"
}
}
}🟢get_pattern(slug, number, framework)
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).
入力スキーマ
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "permanent identity, e.g. \"velocity-image-bend\" — preferred"
},
"number": {
"type": "string",
"description": "pattern number, e.g. \"84\" — a permanent alias for the slug"
},
"framework": {
"type": "string",
"enum": [
"react",
"vue",
"svelte",
"vanilla"
],
"description": "component wrapper format (default: raw HTML/CSS/JS)"
}
}
}🟢get_kit
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.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢get_design_digest
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.
入力スキーマ
{
"type": "object",
"properties": {}
}🟢check_updates(since)
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 alongside the code you generate.
入力スキーマ
{
"type": "object",
"properties": {
"since": {
"type": "string",
"description": "The library version you built against. Omit to just read the current one."
}
}
}🟢recommend_patterns(intent, role, count, context, seed, ...)
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.
入力スキーマ
{
"type": "object",
"properties": {
"intent": {
"type": "string",
"description": "What you are building, e.g. \"premium SaaS landing page for enterprise AI startup\" or \"dark minimal portfolio with dramatic 3D hero\""
},
"role": {
"type": "string",
"description": "Optional page-role filter (hero, nav, pricing, footer, background, etc.)"
},
"count": {
"type": "number",
"description": "Max results (default 5, max 20)"
},
"context": {
"type": "array",
"items": {
"type": "string"
},
"description": "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, and a WebGL pattern in context or in the results auto-adds device-tier-gate (245) as the fallback."
},
"seed": {
"type": [
"string",
"number"
],
"description": "Reproducible creative seed. The same brief and seed return the same candidates; change it to explore another valid realization."
},
"history": {
"type": "array",
"items": {
"type": "string"
},
"description": "Recently used pattern slugs or numbers. They receive a strong cooldown penalty instead of dominating every session."
},
"exclusions": {
"type": "array",
"items": {
"type": "string"
},
"description": "Pattern slugs or numbers that must not be returned."
}
},
"required": [
"intent"
]
}⚪propose_directions(brief, seed)
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.
入力スキーマ
{
"type": "object",
"properties": {
"brief": {
"type": "string",
"description": "Business, audience, offer, conversion goal, real assets, and brand constraints."
},
"seed": {
"type": [
"string",
"number"
],
"description": "Reproducible creative seed."
}
},
"required": [
"brief"
]
}🟢build_page(intent, acts, direction_id, seed, history, ...)
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. PREMIUM FLOOR: load-bearing acts (arrival, proof, action, close) compose only from visually graded S/A patterns. When no S/A exists for one of those slots the result carries premium.shippable=false, the exact gaps, and a redress prescription naming the patterns that would unblock them — do not build or present a composition flagged not-shippable as premium. No argument disables this.
入力スキーマ
{
"type": "object",
"properties": {
"intent": {
"type": "string",
"description": "What the page is for, e.g. \"luxury real estate landing page\" or \"SaaS startup launch with pricing\""
},
"acts": {
"type": "number",
"description": "Number of acts (default 6, range 5–7)"
},
"direction_id": {
"type": "string",
"description": "One direction_id returned by propose_directions for this same intent/seed."
},
"seed": {
"type": [
"string",
"number"
],
"description": "Reproducible creative seed."
},
"history": {
"type": "array",
"items": {
"type": "string"
},
"description": "Recently used pattern slugs or numbers to cool down."
},
"exclusions": {
"type": "array",
"items": {
"type": "string"
},
"description": "Pattern slugs or numbers that must not be used."
}
},
"required": [
"intent"
]
}🟡validate_combination(components)
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.
入力スキーマ
{
"type": "object",
"properties": {
"components": {
"type": "array",
"description": "Pattern slugs or numbers to validate together",
"items": {
"type": "string"
},
"minItems": 2,
"maxItems": 20
}
},
"required": [
"components"
]
}🟢audit_page(html, url)
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 (skeleton order, uniform scaffolding, default type/motion), and prescriptions: real Motion Menu patterns to replace each flagged section, drawn from the same graph recommend_patterns/validate_combination use, plus the exact next tool calls to fetch and validate them. FREE, no key required.
入力スキーマ
{
"type": "object",
"properties": {
"html": {
"type": "string",
"description": "the page's full HTML — one page per call; a multi-page site is the caller's own loop"
},
"url": {
"type": "string",
"description": "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)"
}
}
}🟢adapt_pattern(slug, brand)
Adapt a pattern to a brand system. Pass a pattern slug/number and a brand (colors, typography, spacing, radius) and get back the pattern's HTML/CSS/JS with every visual token replaced by the brand's values. The pattern's behavior, motion, and structure are preserved — only its visual expression changes. This is how a client gets THEIR pattern, not a generic one. FREE, no key required.
入力スキーマ
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "pattern slug or number to adapt"
},
"brand": {
"type": "object",
"description": "the brand system to adapt to",
"properties": {
"name": {
"type": "string"
},
"colors": {
"type": "object",
"properties": {
"primary": {
"type": "string"
},
"secondary": {
"type": "string"
},
"accent": {
"type": "string"
},
"background": {
"type": "string"
},
"text": {
"type": "string"
}
},
"required": [
"primary",
"secondary",
"accent",
"background",
"text"
]
},
"typography": {
"type": "object",
"properties": {
"heading": {
"type": "string"
},
"body": {
"type": "string"
}
},
"required": [
"heading",
"body"
]
},
"spacing": {
"type": "string",
"enum": [
"compact",
"comfortable",
"spacious"
]
},
"radius": {
"type": "string",
"enum": [
"sharp",
"rounded",
"pill"
]
}
},
"required": [
"name",
"colors",
"typography",
"spacing",
"radius"
]
}
},
"required": [
"slug",
"brand"
]
}⚪critique_page(html)
Critique a composed page for mechanical design flaws before shipping. Checks for AI-gradient tells, default typography, dead frames, contrast failures, repeated section grammar, motion-safety gaps, placeholder copy, and slop grammar. Returns a score (0-100) and each finding with its evidence and a fix. This is deterministic markup analysis, not visual review — it cannot judge composition or alignment. FREE, no key required.
入力スキーマ
{
"type": "object",
"properties": {
"html": {
"type": "string",
"description": "the page's full HTML"
}
},
"required": [
"html"
]
}🟢search_patterns(query, count)
Find patterns by meaning, not by keyword. Uses TF-IDF + cosine similarity over the full catalogue metadata (title, tags, style, industry_fit, role, tech). Returns the top-N most semantically related patterns with a relevance score. Use this when recommend_patterns misses because the brief uses different vocabulary than the tags. FREE, no key required.
入力スキーマ
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "what you are looking for, in natural language"
},
"count": {
"type": "number",
"description": "max results (default 10, max 20)"
}
},
"required": [
"query"
]
}⚪verify_complete(html, slugs)
Discharge the release contract before shipping. Checks 11 requirements against your finished markup — reduced-motion strategy, viewport, visible focus, 44px touch targets, alt text, form labels, no debug spew, no placeholder copy, the recorded manifest version, that every pattern you claim resolves, and that no heavy runtime downloads on the reduced-motion path — and returns each failure with the exact fix. Then returns the 7 browser-only passes (desktop/mobile render, alignment, visual critique, fast-scroll lifecycle, accessibility audit, cold route) as OUTSTANDING with the command that discharges each. Those are never marked pass: this tool does not run a browser and does not pretend to. FREE, no key required.
入力スキーマ
{
"type": "object",
"properties": {
"html": {
"type": "string",
"description": "the finished page's full HTML"
},
"slugs": {
"type": "array",
"items": {
"type": "string"
},
"description": "optional — every pattern slug/number the page uses. Defaults to any data-mm-pattern attributes found in the markup; each is checked against the live catalogue so a typo or a renamed slug is caught here rather than as a 404 in the customer's build."
}
},
"required": [
"html"
]
}🟢verify_repair(html, baseline_score, baseline)
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.
入力スキーマ
{
"type": "object",
"properties": {
"html": {
"type": "string",
"description": "the rewritten page's full HTML"
},
"baseline_score": {
"type": "number",
"description": "optional — the ai_shaped_score from the prior audit_page call, for a pass/fail delta"
},
"baseline": {
"type": "object",
"description": "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"
}
},
"required": [
"html"
]
}コミュニティ
エビデンス