HyperCodeMotion MCP

HyperCodeMotion MCP

Connect Claude to HyperCodeMotion, an editor for data-driven motion graphics. Claude designs the animation; this connector checks it and turns it into a .hcmotion project you open in HyperCodeMotion Studio, where you change texts, colors, timing and order yourself instead of asking the AI to regenerate everything.

• MCP endpoint: https://mcp.hypercodemotion.com/mcp (remote, streamable HTTP)
• Authentication: none. The service has no accounts and reads no data from your Claude account.
• Studio: app.hypercodemotion.com

Use it in Claude

1. In Claude, open Settings → Connectors and choose Add custom connector.
2. Name it HyperCodeMotion and paste https://mcp.hypercodemotion.com/mcp.
3. In a chat, turn the connector on from the tools menu.
4. Ask for an animation, or paste a prompt copied from HyperCodeMotion Studio («Crear con IA» → «Generar prompt»).
5. Claude replies with two links:
   • Open: opens the project directly in HyperCodeMotion Studio.
   • Download: the .hcmotion file, which you can also open from the Studio home screen («Cargar proyecto»).

Both links expire 24 hours after they are created. Save the project from Studio (Archivo → Guardar proyecto) to keep it.

Example prompts

• “Create a 15-second vertical launch video for Nimbus, a note-taking app with AI, and give me the HyperCodeMotion project.”
• “Make a 10-second explainer with three steps for brewing pour-over coffee, 16:9, and package it for HyperCodeMotion.”
• “Which layer types and effects does HyperCodeMotion support?”

Tools

The recreation itself happens in the user's own Claude conversation; the connector gives the brief and the reference frames, and returns the comparison with the original. It does not render video for users, generate images, audio or video with AI models, or access anything outside the request it receives.

Data and privacy

• get_capabilities, get_template, validate_json and get_proposal_status store nothing.
• get_recreation_brief stores reference frames of the public source video in the private store (never published), so the recreation can be compared with it.
• propose_template stores the proposal, its card and its source link (no personal data) until a moderator publishes it, which commits it to the Studio code. A salted hash of the moderator's name is kept for one day to limit proposals to 20 a day per moderator.
• create_hcmotion stores the generated file in a private Vercel Blob store. Anyone with the link can download it until it expires after 24 hours; a daily job deletes expired files (at most about 48 hours after creation).
• No accounts, cookies, tracking or AI training on your content.

Gallery templates (setup)

A moderator sends Claude the link of a prompt-motion.com or oneshotted.io video and their moderator code; that is enough for Claude to recreate it, compare it and publish it. The Studio repository's community-render workflow extracts the reference frames, renders the comparisons (sheet and comparacion.mp4, readable by a moderator at GET /api/community?op=compare&id=c-…&file=comparacion.mp4 with their code as bearer) and, on publication (kind: official), renders the gallery media, commits the template to apps/studio/public on its own branch plantilla/<slug> and opens a pull request against TEMPLATE_BRANCH (default template), so each template has its own preview to approve or discard: plantillas/<slug>-<variant>.json, bienvenida/ejemplos/<slug>-<ratio>.{mp4,jpg} and its card in the gallery. Environment variables in this Vercel project: GITHUB_DISPATCH_TOKEN (fine-grained token with Contents: read and write on jasp402/HyperCodeMotion, used only to start that workflow), no shared secret with the workflow: its callbacks carry GitHub's OIDC token (audience hypercodemotion-mcp, repository RENDER_REPO, default jasp402/HyperCodeMotion), checked here against GitHub's keys (COMMUNITY_RENDER_SECRET is still accepted while set), TEMPLATE_ADMIN_CODES or COMMUNITY_ADMIN_SECRET (moderator codes: one code, or name:code, name:code; codes shorter than 6 characters are ignored) and optionally TEMPLATE_BRANCH.

Full details: Privacy Policy · Terms of Service · Support

Support

Email jasp402@gmail.com (also hypercodemotion@gmail.com) or open a GitHub issue. Issues are public: never post passwords, tokens or confidential project content.

For developers

Protocol

The server speaks JSON-RPC 2.0 over HTTP POST (initialize, ping, tools/list, tools/call). A GET on the endpoint returns 405 with a short explanation, which is expected. Request bodies are limited to 4 MB.

.hcmotion layout

It is not encrypted: the SHA-256 only detects truncated or edited files. Studio implements the same layout in packages/core/src/hcmotion.ts.

Files are served at https://mcp.hypercodemotion.com/d/<id> and open in Studio at https://app.hypercodemotion.com/?p=<id>. After 24 hours the link returns 410.

Deployment settings

• A private Blob store connected to the Vercel project. It authenticates through OIDC (BLOB_STORE_ID + the project's OIDC token); a BLOB_READ_WRITE_TOKEN also works.
• CRON_SECRET so only Vercel Cron can call /api/cleanup.
• Optional PUBLIC_URL / STUDIO_URL (default https://mcp.hypercodemotion.com / https://app.hypercodemotion.com).

Testing

npm test          # unit and integration tests
npm run test:live # smoke test against production

GitHub Actions runs both. Neither guarantees full Studio rendering compatibility.

Capabilities snapshot

The catalog is derived from Studio source files (packages/core/src/schema.ts, packages/core/src/presets.ts) and must be reviewed when Studio changes.

HyperCodeMotion Creative Skill

The repository also contains the HyperCodeMotion Agent Skill, which guides AI assistants from brief to art direction, scenes, editable JSON and the .hcmotion handoff. It is distributed separately from the connector and does not activate just because the connector is connected.

License

Source code: Apache License 2.0. The hosted service is subject to the Terms of Service. HyperCodeMotion names and logos are not licensed by the software license.