HyperCodeMotion MCP

Open-source, read-only Model Context Protocol server for HyperCodeMotion.

• MCP endpoint: https://mcp.hypercodemotion.com/mcp
• Current tools: get_capabilities, validate_json
• Formats recognized: composition (layers), design (elements), improvement patch (add, change, remove, sfx)
• Deployment: GitHub main → Vercel; production smoke checks run in GitHub Actions

What it does and does not do

The current service checks JSON structure and compares layer properties/effect IDs to a source-pinned snapshot of HyperCodeMotion Studio's supported features. Validation is preliminary and results explicitly indicate fullyValidated: false.

The current service does not create or persist projects, modify Studio, export video, render animations, or guarantee that a passing JSON will work visually in Studio. Proposed future tools are not yet available.

Connect

Configure a compatible MCP client with the remote endpoint:

https://mcp.hypercodemotion.com/mcp

The server responds to HTTP POST JSON-RPC messages; browsing to the URL with GET returns {"error":"POST required"}, which is expected.

Available tools

Name	What it provides
get_capabilities	Snapshot of supported layer types, properties, effect preset slots and source identifiers
validate_json	Structural check of a JSON object or JSON string, with warnings/errors; optionally supply the existing composition for improvement patches

Testing

npm test
npm run test:live

GitHub Actions runs unit tests and a separate production smoke test. Neither the unit tests nor the smoke test guarantee full Studio rendering compatibility.

HyperCodeMotion Creative Skill

The repository also contains the HyperCodeMotion Agent Skill. It guides AI assistants through brief → visual references → art direction → scenes → editable JSON → MCP validation → Studio import. Specialized references explain composition formats, motion, visual design, HTML scene assets and validation. A sample JSON and automated checks are included.

The Skill is available as repository files; publication to external Skill catalogs and installation in individual AI clients are separate future steps. It does not automatically activate merely because the MCP is connected.

Privacy, Terms & Support

The following apply only to this MCP service, not HyperCodeMotion Studio:

• Privacy Policy
• Terms of Service
• Support

Support: GitHub Issues. Issues are public; never share sensitive project data or access tokens.

Source and license

The catalog snapshot was derived from Studio source files including packages/core/src/schema.ts and packages/core/src/presets.ts. The MCP repository does not modify Studio. Snapshot updates must be reviewed when Studio changes.

Source code is available under Apache License 2.0. The hosted MCP service is separately subject to the Terms of Service.

Roadmap (not yet implemented)

• Verify full import/merge compatibility using the Studio rules, rather than structural checks alone.
• Improve validation and developer documentation.
• Implement authenticated project operations if the product requires them.
• Prepare for applicable public MCP/plugin directory review.