Motion Menu is an MCP server with 11 tools an agent can call, among them audit_page, build_page, check_updates. It answers at https://www.motionmenu.ca/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
597 motion/3D UI patterns as ready HTML/CSS/JS, served over MCP. The entire library is free.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: html, url |
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, 1 Inputs: intent, acts, direction_id, seed, history, exclusions |
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 — s Inputs: since |
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. |
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_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). Inputs: slug, number, framework |
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 Inputs: query, role, tag, collection, section |
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 di Inputs: brief, seed |
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, reas Inputs: intent, role, count, context, seed, history |
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-fl Inputs: components |
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 STIL Inputs: html, baseline_score, baseline |
Every block below points at https://www.motionmenu.ca/api/mcp. Pick your client and copy.
claude mcp add --transport http motion-menu https://www.motionmenu.ca/api/mcp
{
"mcpServers": {
"motion-menu": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.motionmenu.ca/api/mcp"]
}
}
}{
"mcpServers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"servers": {
"motion-menu": {
"type": "http",
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"context_servers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"mcpServers": {
"motion-menu": {
"serverUrl": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"mcpServers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}name: Motion Menu
version: 0.0.1
schema: v1
mcpServers:
- name: Motion Menu
type: streamable-http
url: https://www.motionmenu.ca/api/mcp{
"mcpServers": {
"motion-menu": {
"httpUrl": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"mcpServers": {
"motion-menu": {
"type": "http",
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}{
"mcpServers": {
"motion-menu": {
"url": "https://www.motionmenu.ca/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.motionmenu.ca%2Fapi%2Fmcp&type=streamable_http&id=motion-menu&name=Motion%20Menu
It answered our last check on 22 October 2026 in 187 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
11, as returned by the server's own tools/list on 14 September 2026: audit_page, build_page, check_updates, get_design_digest, get_kit, get_pattern, list_patterns, propose_directions, and 3 more.
It answered our last check on 22 October 2026 in 187 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.motionmenu.ca/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.dev55acc-ai. Endpoint host: www.motionmenu.ca. ARD identifier: urn:air:io.github.dev55acc-ai:mcp:motion-menu.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.