For agents

Connect your agent

One MCP endpoint, one shadcn registry, one plain HTTP surface — all backed by the same 596-pattern catalogue. Point any of them at Motion Menu and start composing.

Claude Code

The key stays in your environment, not your command history:

export MOTION_MENU_KEY="mm_live_..."
claude mcp add --transport http motion-menu \
  https://motion-menu-two.vercel.app/api/mcp \
  --header "Authorization: Bearer ${MOTION_MENU_KEY}"

Cursor / Windsurf

Add a block to your MCP config file:

{
  "mcpServers": {
    "motion-menu": {
      "url": "https://motion-menu-two.vercel.app/api/mcp",
      "headers": { "Authorization": "Bearer ${MOTION_MENU_KEY}" }
    }
  }
}

Any other MCP-capable client connects the same way — it is a single streamable-http POST endpoint, JSON-RPC 2.0.

Plain HTTP

No MCP client? Every pattern is one request:

curl -H "Authorization: Bearer mm_live_..." \
  https://motion-menu-two.vercel.app/p/150.json

# the index and the cheatsheet are public, no key
curl https://motion-menu-two.vercel.app/kit.md
curl https://motion-menu-two.vercel.app/llms.txt

shadcn registry

Every pattern ships as React, Vue, Svelte, or vanilla TS:

npx shadcn@latest add "https://motion-menu-two.vercel.app/r/<slug>.json?framework=react"

Workflow

initialize teaches the call order on connect. Read get_design_digest first — the anti-generic rules a composition has to respect — then recommend_patterns and validate_combination to pick and check a set before building. compose_page turns a validated set into one working page; get_pattern pulls one pattern's full code. get_kit is the one-call shortcut: design laws plus the full index in a single response.

Free vs. paid

The rest of the 596 patterns, every theme beyond mm, and compose_page — plan or build mode, both — need the Lifetime plan: $149 once, forever, no subscription. A refused call answers with what plan would unlock it, not just an error code.

Motion Menu · Catalogue · Store · Docs · Terms · Privacy