Motion Menu Director v1 — MCP server
Motion Menu is an agent-facing design director backed by 597 transplantable motion and UIpatterns. It helps a coding agent establish a visual direction, plan the complete page, validatethe component set, and retrieve the selected HTML/CSS/JS or framework wrappers.
The entire 597-pattern library is free. No entitlement key, card, tier, seat, or subscription isrequired.
MCP endpoint
https://www.motionmenu.ca/api/mcp
The endpoint uses JSON-RPC 2.0 over streamable HTTP. Start with initialize, then treattools/list as the runtime authority for available tools and their schemas.
Connect
Codex:
codex mcp add motion-menu --url https://www.motionmenu.ca/api/mcp
Claude Code:
claude mcp add --transport http motion-menu https://www.motionmenu.ca/api/mcp
Cursor / Windsurf (mcp.json):
{
"mcpServers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}
Cline: see llms-install.md.
Claude Code plugin (optional — the same endpoint plus the Motion Menu workflow skill):
/plugin marketplace add Nimos-Websites/motion-menu-plugin
/plugin install motion-menu-patterns@motion-menu
Director workflow
Use this path when the user asks Motion Menu to design, elevate, redesign, or add motion withoutnaming an exact pattern:
get_design_digest {}— read the machine-readable quality and implementation contract.propose_directions {brief, seed}— generate three materially different design genomes fromthe business, audience, offer, primary action, real assets, and constraints.- Choose one returned
direction_id. build_page {intent, direction_id, seed, history, exclusions}— plan the whole page. Copy theexact directionbriefintointentand reuse the same seed; pass recently used patterns inhistoryand hard vetoes inexclusions.validate_combination {components}— check the complete selected set and resolve hardviolations before implementation.get_pattern {slug}— retrieve only the approved pattern bodies. Addframeworkwithreact,vue,svelte, orvanillawhen a wrapper is useful.
Example arguments:
{
"brief": "Independent architecture practice serving cultural institutions. Primary action: book a portfolio review. Real project photography is available.",
"seed": "practice-launch-02"
}
After selecting a returned direction, use the exact brief as intent:
{
"intent": "Independent architecture practice serving cultural institutions. Primary action: book a portfolio review. Real project photography is available.",
"direction_id": "<returned direction_id>",
"seed": "practice-launch-02",
"history": ["<recently used slug or number>"],
"exclusions": ["<slug or number that must not recur>"]
}
Director output is a page plan, not a rendered website. The host coding agent still adapts thepatterns to the real design system, implements them in the target repository, and verifies theresult in a browser at desktop and mobile widths.
Manual pattern mode
An explicit pattern choice bypasses autonomous selection. If a user names a number or slug, callget_pattern directly and honor it:
{ "number": "150", "framework": "react" }
Numbers are permanent aliases; slugs are preferred in code and build records. Manual lookupremains available even when a pattern is excluded from autonomous recommendations.
Without an MCP client, pattern bodies are also available over plain HTTP:
curl https://www.motionmenu.ca/p/150.json
curl https://www.motionmenu.ca/p/velocity-image-bend.md
Supporting tools
The current server also exposes:
list_patternsfor catalogue discovery and filtering.get_kitfor the complete design laws and pattern index.recommend_patternsfor quality-gated candidates within a narrower role or intent.check_updatesfor catalogue-version and changed-pattern checks.audit_pageandverify_repairfor deterministic HTML-grammar repair checks on existing pages.
audit_page and verify_repair do not render a page or judge screenshots. Visual inspection,accessibility testing, runtime cleanup, and release verification remain the host agent's job.
Other interfaces
The shadcn registry can retrieve a pattern wrapper directly:
npx shadcn@latest add "https://www.motionmenu.ca/r/<slug>.json?framework=react"
Links
This repository contains the public registry metadata and install documentation forio.github.MotionMenu/motion-menu. The implementation and pattern source remain in the mainMotion Menu repository.