magic-hour-media
Magic Hour media
Deliver a usable image, video, or audio result. A queued project ID is an intermediate result unless the user asked only to submit a job.
Requires network access and either a connected Magic Hour MCP server or a Magic Hour API key with an HTTPS-capable runtime. Generation consumes Magic Hour credits.
Work from the user's goal
Accept ordinary requests such as “put me in this clip,” “make my character do this” or “turn this portrait into an impossible scene.” Infer the placement and creative direction from supplied context; recommend one direction when needed. Ask only for missing information that changes the result or spending authority, not model names, schema fields or a completed prompt template. When creative choices are delegated, inspect and accept suitable intermediate assets yourself and continue. Respect requested review points and the existing budget. Lead delivery with the actual media; keep IDs and technical records in the project unless they are needed to explain a failure. For transformations or recreating a visual format, read the remix workflow; for music, read music and performance.
Connect to the right service
Use an already-connected Magic Hour creation MCP if available. Its hosted endpoint is https://mcp.magichour.ai/. The separate https://docs.magichour.ai/mcp searches documentation; it does not generate media.
If creation tools are unavailable, read references/setup.md in this skill for setup and the API fallback. Do not silently replace an existing client configuration. Never request an API key in chat or put it in source code; use the client's credential flow or MAGIC_HOUR_API_KEY in the local environment.
Use live tool schemas, or the API documentation index, for current models, allowed durations, resolutions, and prices. Web-app features and plans do not imply identical API support. Do not copy a remembered model catalog or price table.