All servers · Code & repositories · Research & knowledge · AI models & agents

Motion Menu

io.github.dev55acc-ai/motion-menu · v16.0.0

Measured by MCP Station

Description written by the publisher, not verified

597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free.

Connect

claude mcp add --transport http motion-menu https://www.motionmenu.ca/api/mcp

{
  "mcpServers": {
    "motion-menu": {
      "url": "https://www.motionmenu.ca/api/mcp"
    }
  }
}

Tools as reported by the server

• list_patterns
  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
• get_pattern
  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).
• 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.
• 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.
• check_updates
  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 wi
• recommend_patterns
  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 actua
• propose_directions
  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.
• build_page
  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_patte
• validate_combination
  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 position
• audit_page
  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 matche
• verify_repair
  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 ke

Website · JSON · Text for agents · Registry updated 2026-09-01